Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-1828

Add support to Shielded VMs on GCP

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • openshift-4.13
    • None
    • Add support to Shielded VMs on GCP
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-632 - Add support to Shielded VMs on GCP
    • OCPSTRAT-632Add support to Shielded VMs on GCP
    • 0
    • 0% 0%

      Epic Goal

      • Support OpenShift and the IPI workflow on GCP to use Shielded VMs feature from Google Cloud

      Why is this important?

      • Many Google Cloud customers want to leverage Shield VMs feature while deploying OpenShift on GCP

      Scenarios

      1. As a user, I want to be able to instruct the OpenShift Installer to use Shield VMs while deploying the platform on Google Cloud so I can use the Shield VMs feature 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.

      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>

       

            joelspeed Joel Speed
            mak.redhat.com Marcos Entenza Garcia
            Milind Yadav Milind Yadav
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: