You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OCPBUGS-33787: Tolerate the absence of ingress capability on HyperShift clusters
- Implement alternative ingress fields from the console operator config API
- Skip component route customizations if ingress capability is disabled
- Use NodePort type for console and downloads services if ingress capability is disabled
- Add document to describe how to implement alternative ingress on ROSA
2. When the ingress capability is disabled, the console operator relies on the end user to provide the console and download URLs (using the operator API) for health checks and oauthclient.
106
+
107
+
3. When the ingress capability is disabled, the console operator skips the implementation of the component route customization.
108
+
109
+
4. To simulate the absence of ingress connectivity when the ingress capability is disabled, set the desired replicas to zero in the default ingress controller:
0 commit comments