-
Bug
-
Resolution: Not a Bug
-
Normal
-
4.18.0
-
None
-
None
-
Installer Sprint 262
-
1
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
When UserProvisionedDNS is enabled on AWS, add Ingress LB IPs to the Infrastructure CR. CoreDNS pods running within the cluster would use the LB IP value within the Infra CR to provide DNS resolution for *.apps. On the AWS platform, on the `Hostname` of the Ingress LoadBalancer is available. Until we find a better alternative, lookup the IP address associated with the `Hostname` and add the resulting IP address into the Infra CR. https://github.com/openshift/cluster-ingress-operator/pull/1167 has already merged on master and needs to be backported to 4.18.0
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- depends on
-
OCPBUGS-44907 Add Ingress LB IPs to status field of Infrastructure CR
- Closed