Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-2339

OpenShift using encrypted vSphere VMs (UPI)

XMLWordPrintable

    • OpenShift using encrypted vSphere VMs (UPI)
    • BU Product Work
    • False
    • None
    • False
    • Not Selected
    • Done
    • OCPSTRAT-322 - vSphere VMcrypt support (UPI)
    • OCPSTRAT-322vSphere VMcrypt support (UPI)
    • 0% To Do, 0% In Progress, 100% Done

      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

      • As an Infrastructure Administrator, I want to deploy OpenShift on vSphere 7.x+ using encrypted vSphere VMs with UPI. 

      Why is this important?

      • This is a requirement for some customers who are under strict security regulations.

      Scenarios

      1. This is a test-only for UPI + encrypted VMs + setup KMS.
      2. Document unsupported operations or limitations, if any.

      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. This epics requires the OCP VMs to be encrypted with KMS, we first need to support this scenario.
      2. We need to scope the VMWare support coverage & limitation.
      3. STOR-1058 (vSphere CSI encryption support) needs to be completed alongside this epic.

       

      Contributing Teams(and contacts) (mandatory) 

      • QE team and/or SPLAT team for supporting encrypted VMs.

      Previous Work (Optional):

      Open questions:

       

      Drawbacks or Risk (optional)

      • Increases vSphere support matrix. Support may be more complex due to encryption.

      Done Checklist

      The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

      • 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 scenarios are written and executed successfully.
        • Test plans in Polarion: <link or reference to Polarion>
        • Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>
      • TE (Technical Enablement) - Slides are complete (if requested by PLM)
      • All associated work items with the Epic are closed
      • Epic status should be “Release Pending” 

       

       

       

       

          1.
          Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          PX Tracker Sub-task Closed Undefined Unassigned
          3.
          QE Tracker Sub-task Closed Undefined Shang Gao
          4.
          TE Tracker Sub-task Closed Undefined Unassigned

              sgaoshang Shang Gao
              julim Ju Lim
              Shang Gao Shang Gao
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: