OCP/Telco Definition of Done
Epic Template descriptions and documentation.

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

This feature introduces official support for VMware Cloud Foundation 9 (VCF9) as a target platform for OpenShift Container Platform (OCP). This enables customers to deploy, manage, and upgrade OCP clusters on the VCF9 infrastructure, ensuring they can leverage the newest capabilities and improvements of the VMware stack while maintaining full feature parity and support from Red Hat.

The primary goal is to certify and support VCF9 for OCP installations and upgrades, providing a seamless experience for administrators across all installation methods.

The user will be able to:

• Successfully install OpenShift 4.17+ on VCF9 using all supported installation methods: Installer-Provisioned Infrastructure (IPI), User-Provisioned Infrastructure (UPI), Assisted Installer, and Agent-based Installer (ABI).
• Perform OCP cluster upgrades (z-stream and y-stream) on a VCF9 environment.
• Utilize all existing OCP on vSphere features with the same level of functionality as on previous vSphere 8.
• Use Hive or RHACM to manage OCP on VCF9.

VCF9 requires a minimum vSphere CSI driver 3.4.0 to support Kubernetes 1.30+, which means that below OpenShift versions can be supported:

• • (PRIO 2) OpenShift 4.17
  • (PRIO 2) OpenShift 4.18
  • (PRIO 2) OpenShift 4.19
  • (PRIO 1) OpenShift 4.20

Why is this important?

• It impacts any OpenShift on vSphere 8 deployment.

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Hive and RHACM can manage OCP clusters on VCF9 (as it is with vSphere 8).

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>