• Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • TP1
    • None
    • None
    • None
    • Serverless Sprint 171

      Currently, the operator only pays attention to CR's created in the `knative-serving` namespace that are named `knative-serving`. Is this what we want?

      Open Questions:
      1) does the console guide the user to create the CR in a valid ns, i.e. not "openshift-operators"?
      2) does monitoring/metrics require the CR to reside in a particular ns?

      The operator doesn't care, and will happily create knative-serving in whatever ns the CR lives in... once we remove the existing restriction.

              jcrossle@redhat.com Jim Crossley
              jcrossle@redhat.com Jim Crossley
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: