Epic Goal

 
Deploy with IPI while disabling the built-in LB (keepalived/haproxy) and allowing to configure manually an external LB for the api/ingress.

Why is this important?

The main request comes from a major customer using platform vSphere and deploying with IPI. Their goal is to use zoning for OpenShift, which includes different subnets, while keeping the IPI installation flow for OpenShift on vSphere.

They also want to use their own external load balancer for API and Ingress instead of the built-in one based on keepalived/haproxy for their production environments.

This will be useful to any customers who want the benefits of the automation via the IPI installer on vSphere and want to leverage their external load balancers to access their production clusters.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• 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>