Epic Goal

• Customers should be able to update OpenShift on vSphere without impacting their existing zonal configurations (e.g. multiple data centers in a single vCenter) and without having to perform any unique actions to persist and/or maintain their zonal configuration. Additionally, existing workloads that leverage zonal configurations will continue to function as they always have to enable a smooth transition for end users.

Out of scope:

Customers will not be permitted to update/migrate OpenShift on vSphere from a non-zonal configuration to a zonal configuration.

Why is this important?

• Multiple customers have requested OpenShift on vSphere to support zonal configurations (multiple data centers in a single vCenter), and we need to ensure those clusters can be upgraded smoothly.

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

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>