-
Feature Request
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
-
-
1. Proposed title of this feature request
Openshift Ingress Controller provisions static/predefined IP for the cloud service load balancer
2. What is the nature and description of the request?
In AWS/Azure/GCP, when an ingress controller is created. The IP address of the ingress endpoint Load balancer IP is randomly assigned for both internal and public load balancers. We want this IP to be more predictable and be a static IP.
3. Why does the customer need this? (List the business requirements here)
Firewalls and DNS changes are usually lengthy ticketing systems in enterprises.
- Not all customers allow firewalls open with a big range. They need a specific IP to be configured in their firewall in advance.
- It is not ideal to reconfigure the firewall when the openshift cluster was rebuilt in the cloud
- Same for DNS configuration. Without knowing a fixed IP, the DNS needs to be reconfigured once the IP is changed.
4. List any affected packages or components.
Ingress Operator https://docs.openshift.com/container-platform/4.7/networking/ingress-operator.html
- duplicates
-
RFE-2824 IngressController should support the definition of loadBalancerIP on the LoadBalancer service
- Under Review