Uploaded image for project: 'Knative Serving'
  1. Knative Serving
  2. SRVKS-590

It's possible to accidentally deploy Knative Serving into the wrong namespace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.14.0
    • 1.7.1
    • Operator
    • Serverless Sprint 197, Serverless Sprint 198

      On a fresh cluster, install OpenShift Serverless and immediately create a KnativeServing instance using the UI in the openshift-operators namespace it drops you into. When I did this, it ended up actually deploying a full Knative Serving control plane in my openshift-operators namespace instead of preventing me or telling me this should only be in the knative-serving namespace.

      We should never allow the user to get a working Knative Serving control plane in a namespace other than `knative-serving` until/unless we later decide to change or relax that restriction.

              markusthoemmes Markus Thömmes (Inactive)
              bbrownin@redhat.com Ben Browning
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: