-
Epic
-
Resolution: Done
-
Normal
-
None
-
External load balancers with vSphere IPI
-
BU Product Work
-
False
-
False
-
To Do
-
OCPSTRAT-264 - Compute and control plane nodes on separate subnets for on-prem IPI [ Phase 1]
-
Impediment
-
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
As an OpenShift infrastructure owner I need to deploy OCP on vSphere with the installer-provisioned infrastructure workflow and configure my own load balancers
Why is this important?
Customers want to use their own load balancers and IPI comes with built-in LBs based in keepalived and haproxy.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- Documentation
Previous Work
This has been tested successfully https://bugzilla.redhat.com/show_bug.cgi?id=1986964#c2 (needs docs update and QE)
OSP and bare metal IPI already include this option:
Bare Metal epic in 4.8: KNIDEPLOY-4421
OSP epic in 4.7: OSASINFRA-2085
We expect to be able to add the same to vSphere without code changes.
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- 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>
- is related to
-
RFE-2054 Allow customers to use their own LB for external api/ingress traffic for OCP 4 IPI VMware installs.
-
- Accepted
-
- links to
1.
|
Docs Tracker |
|
Closed | 
|
James Brigman |
|
|||||||
2.
|
QE Tracker |
|
Closed |
|
Jinyun Ma | ||||||||
3.
|
TE Tracker |
|
Closed |
|
Eric Rich | ||||||||
4.
|
PX Tracker |
|
Closed |
|
Eric Rich |
