Epic Goal

• Support OpenShift and the IPI workflow on GCP to use Confidential Compute service from Google Cloud

Why is this important?

• Google Cloud customers want to leverage confidential compute service while deploying OpenShift on GCP

Scenarios

1. As a user, I want to be able to instruct the OpenShift Installer to use confidential VMs while deploying the platform on Google Cloud so I can use the confidential compute service from GCP on every Node.

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. POC:
   1. Create rhcos image on gcp with the required guest-os-feature tags (see COS-1794)
   2. openshift/installer 
   3. openshift/api
   4. openshift/machine-api-provider-gcp
2. Recorded demo

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>