-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
BU Product Work
-
5
-
False
-
None
-
False
-
OCPSTRAT-346 - Make Ingress Operator optional
-
-
-
Sprint 238, Sprint 239
-
0
-
0.000
Context
HyperShift uses the cluster-version-operator (CVO) to manage the part of the ingress operator's payload, namely CRDs and RBACs. The ingress operator's deployment though is reconciled directly by the control plane operator. That's why HyperShift projects the ClusterVersion resource into the hosted cluster and the enabled capabilities have to be set properly to enable/disable the ingress operator's payload and to let users as well as the other operators be aware of the state of the capabilities.
Goal
The goal of this user story is to implement a new capability in the OpenShift API repository. Use this procedure as example.
- blocks
-
NE-1318 Update the cluster version operator to handle the ingress capability
- Closed
-
NE-1316 Update the openshift installer to handle the ingress capability
- Closed
-
NE-1319 Update the cluster console operator not to go degraded without ingress
- Closed
- is blocked by
-
NE-1310 Enhancement proposal to describe the implementation details
- Closed
- links to