-
Feature
-
Resolution: Done
-
Critical
-
None
-
Strategic Product Work
-
False
-
-
False
-
0% To Do, 0% In Progress, 100% Done
-
L
-
0
-
Program Call
Make it possible to entirely disable the Ingress Operator by leveraging the OCPPLAN-9638 Composable OpenShift capability.
Why is this important?
- For Managed OpenShift on AWS (ROSA), we use the AWS load balancer and don't need the Ingress operator. Disabling the Ingress Operator will reduce our resource consumption on infra nodes for running OpenShift on AWS.
- Customers want to be able to disable the Ingress Operator and use their own component.
Scenarios
- This feature must consider the different deployment footprints including self-managed and managed OpenShift, connected vs. disconnected (restricted and air-gapped), implications for auto scaling, chargeback/showback use scenarios, etc.
- Disabled configuration must persist throughout cluster lifecycle including upgrades
- clones
-
RFE-3395 Make Ingress Operator optional
- Accepted
- depends on
-
NE-1151 AWS ALB operator GA
- Closed
- is blocked by
-
HOSTEDCP-732 [Spike] Making Ingress operator optional
- Closed
-
OBSDA-278 Don't block Cluster Monitoring Operator if Routes aren't accepted
- In Progress
- is incorporated by
-
OCPSTRAT-1308 OpenShift Optional Capabilities (Phase 7)
- New
-
OCPSTRAT-36 OpenShift Optional Capabilities (Phase 4)
- Closed
-
OCPSTRAT-421 OpenShift Optional Capabilities (Phase 5)
- Closed
-
OCPSTRAT-731 OpenShift Optional Capabilities (Phase 6)
- Closed
- is related to
-
NE-1129 Composable OpenShift: Make ingress optional on HyperShift
- Closed
- relates to
-
HOSTEDCP-732 [Spike] Making Ingress operator optional
- Closed
-
OCPSTRAT-1308 OpenShift Optional Capabilities (Phase 7)
- New
-
OCPSTRAT-36 OpenShift Optional Capabilities (Phase 4)
- Closed
-
OCPSTRAT-421 OpenShift Optional Capabilities (Phase 5)
- Closed
-
OCPSTRAT-731 OpenShift Optional Capabilities (Phase 6)
- Closed
-
OCPSTRAT-147 OpenShift Optional Capabilities (Phase 3)
- Closed