-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
Serverless Sprint 184, Serverless Sprint 185, Serverless Sprint 189
As per Engineering: Serverless roadmap brainstorming doc, OpenShift Route, which is currently living in "knative-serving-ingress" namespace, should be living in the same namspace with Knative Services.
With this change, users can customize OpenShift Route and use their own TLS instead of Wildcard Certs.
- is cloned by
-
SRVKS-623 A supported way for developers to manage the OpenShift Routes of their Knative Services to do things like customize the TLS setup without Service Mesh integration
- Closed
- relates to
-
SRVKS-617 [QE] test for "OpenShift Route and Istio VirtualService fronting a Knative Service"
- Closed