-
Feature Request
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
-
-
1. Proposed title of this feature request: support for ingress loadBalancerIP
2. What is the nature and description of the request?
When an ingress controller is deployed with LoadBalancerService as endpointPublishingStrategy should be possible to define the loadBalancerIP of the service exposing the router.
Here an example of CRD:
apiVersion: operator.openshift.io/v1 kind: IngressController metadata: namespace: openshift-ingress-operator name: default spec: endpointPublishingStrategy: type: LoadBalancerService loadBalancer: scope: Internal loadBalancerIP: xxx.yyy.zzz.www
3. Why does the customer need this?
- In this way the cluster admin has control over the public IP used by the ingress router, simplifying the automation of the external LB configuration.
- Without this feature the admin needs to patch the service complicating the management of the cluster.
- If the ingress is for some reasons re-deployed the admin needs to patch again the service.
4. List any affected packages or components.
- Ingress Controller
- is duplicated by
-
RFE-2884 Openshift Ingress Controller provision static/predefined IP for service load balancer
- Deferred
- relates to
-
RFE-6242 Ability to specify a pre-created loadbalancer IP on OpenStack
- Backlog
-
RFE-3498 Need the stable LoadBalancer IP
- Under Review
-
RFE-2127 [GCP] Allow Ingress ILB to define a specific subnet
- Accepted
-
OCPSTRAT-1502 [Outcome] Support external DNS for OpenShift on AWS and Azure
- New
-
OCPSTRAT-261 [Outcome] Support external DNS for OpenShift on GCP
- In Progress