-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
None
-
None
-
Installer Sprint 275, Installer Sprint 276, Installer Sprint 277, Installer Sprint 278, Installer Sprint 279, Installer Sprint 280
Now that custom-dns work is being expanded to Azure, extract Ingress Load Balancer IPs updated by the LoadBalancer service and available via the `LoadBalancerIngress` API.
Follow the same approach used for AWS https://github.com/openshift/cluster-ingress-operator/pull/1167 and GCP https://github.com/openshift/cluster-ingress-operator/pull/1016 .
User Story:
As a (user persona), I want to be able to:
- Capability 1
- Capability 2
- Capability 3
so that I can achieve
- Outcome 1
- Outcome 2
- Outcome 3
Acceptance Criteria:
Description of criteria:
- Upstream documentation
- Point 1
- Point 2
- Point 3
(optional) Out of Scope:
Detail about what is specifically not being delivered in the story
Engineering Details:
- (optional) https://github/com/link.to.enhancement/
- (optional) https://issues.redhat.com/link.to.spike
- Engineering detail 1
- Engineering detail 2
This requires/does not require a design proposal.
This requires/does not require a feature gate.