-
Bug
-
Resolution: Done
-
Major
-
1.7.1
-
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.
- relates to
-
SRVKS-581 Investigation: Using the upstream operator as a library
- Closed