-
Feature Request
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request: LB Service Controller
2. What is the nature and description of the request? OpenShift's default ingress controller today does not track the cloud resource such as Classic or NLB and reconcile to create a new one if the LB associated with the router-default service is deleted.
3. Why does the customer need this? (List the business requirements here) This kind of removal of cloud resources upon which OpenShift services including console and routes are depended upon can cause unavailability of console and application routes published using the OpenShift's ingress controller. As operators manage the life cycle of the resources, the operator must ideally track the status of resources it creates and reconcile to the configured state if there's a drift.
4. List any affected packages or components.
Ingress controller / Operator