Epic Goal

• Add GCP C4/C4A to the tested instances list for OpenShift on GCP

Why is this important?

• This is a new Machine Series Google has introduced that customers will use for their OpenShift deployments

Scenarios

1. Deploy an OpenShift Cluster with both the Control Plane and Compute Nodes running on C4 GCP Machines
2. Deploy an OpenShift Cluster with both the Control Plane and Compute Nodes running on C4A GCP Machines

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. Hyperdisk-balanced enablement work via OCPSTRAT-1496

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>