-
Story
-
Resolution: Done
-
Major
-
None
Installation experience (auto provision namespaces for Service Mesh)
- Automatically install a ServiceMeshControlPlane in a namespace controlled by Knative Serving - this should be a separate namespace from `knative-serving` or `istio-system`
- Automatically enroll any namespace using a Knative Ingress into the ServiceMeshMemberRoll for our ServiceMeshControlPlane unless that namespace is already in another ServiceMeshMemberRoll
- For the sake of users upgrading from our 1.0.0 release, we may want to “adopt” that istio-system ServiceMeshControlPlane as if it was the one we auto-installed in 1.1.0 - not a must-have
- blocks
-
SRVKS-286 As a user that already installed Service Mesh I want to deploy Knative Services in that mesh
-
- Closed
-
- causes
-
SRVKS-305 [DOC] Update Service Mesh sections in OCP Serverless docs
-
- Closed
-
- is blocked by
-
SRVKS-313 Openshift routes override each other for the same Route/Service names in different namespaces
-
- Closed
-
- relates to
-
SRVKS-302 [Obsolete] serverless install docs missing install details
-
- Closed
-