XML

Word

Printable

Epic Name:
confidential compute support on Azure
Blocked:
True
Blocked Reason:
https://issues.redhat.com/browse/OCPBUGS-18379
Ready:
False
Color Status:
Not Selected
Epic Status:
To Do
Feature Link:
OCPSTRAT-366 - [Technology Preview] - Add support for Confidential VMs on Azure
Parent Link:
OCPSTRAT-366[Technology Preview] - Add support for Confidential VMs on Azure
Hierarchy Progress Bar:

0% To Do, 100% In Progress, 0% Done
Target Version:

openshift-4.14

Epic Goal

Support OpenShift and the IPI workflow on Azure to use the respective Confidential Compute service
Allow customers to scale their OCP clusters running on Azure with new confidential compute VMs.

Why is this important?

Azure customers want to leverage confidential compute service while deploying OpenShift on Azure

As a user, I want to be able to instruct the OpenShift Installer to use confidential VMs when deploying the cluster on Azure, so I can use the confidential compute by Azure on every Node.

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

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>