Epic Goal

• Enable users to specify a pre-existing address for the cluster to use for the API load balancer(s).
• Enable users to specify a pre-existing address for the cluster to use for the *.apps ingress load balancer(s).

Why is this important?

• To enable users to configure DNS resolution in advance to installing a cluster
• To enable future to enable Shared VPC clusters to be provisioned using the IPI workflow.

Scenarios

1. When a pre-existing address is added to the install config for the API load balancers, the installer uses it when provisioning those load balancers
2. When a pre-existing address is added to the install config for the default *.apps ingress load balancer, the installer passes this to the cluster where it then uses this address when provisioning the default load ingress load balancers.

Acceptance Criteria

• Release Technical Enablement - Provide necessary release enablement details and documents.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>