Uploaded image for project: 'OpenShift Storage'
  1. OpenShift Storage
  2. STOR-1357

Review and support the work from IBM to enable BYOK in OpenShift on IBM Cloud VPC

    XMLWordPrintable

Details

    • Review and support the work from IBM to enable BYOK in OpenShift on IBM Cloud VPC
    • 1
    • False
    • None
    • False
    • Green
    • To Do
    • OCPSTRAT-663 - Enable BYOK for IBM Cloud VPC
    • OCPSTRAT-663Enable BYOK for IBM Cloud VPC
    • 100
    • 100% 100%
    • XS
    • 1

    Description

      Epic Goal*

      Review and support the IBM engineering team while enabling BYOK support for OpenShift on IBM Cloud VPC

       
      Why is this important? (mandatory)

      As part of the replatform work IBM is doing for their OpenShift managed service this feature is Key for that work

       
      Scenarios (mandatory) 

      All the cluster storage objects, VMs storage and storage managed by StorageClass objects defined in the platform., will be encrypted using the user-managed key provided in the installation manifest

       
      Dependencies (internal and external) (mandatory)

      https://issues.redhat.com/browse/CORS-2694

      Contributing Teams(and contacts) (mandatory) 

      The IBM development team will be responsible of developing this feature and RH engineering team will review and support their work

      Done - Checklist (mandatory)

      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 Testing -  Basic e2e automationTests are merged and completing successfully
      • Documentation - Content development is complete.
      • QE - Test scenarios are written and executed successfully.
      • Technical Enablement - Slides are complete (if requested by PLM)
      • Engineering Stories Merged
      • All associated work items with the Epic are closed
      • Epic status should be “Release Pending” 

      Attachments

        Activity

          People

            jdobson@redhat.com Jonathan Dobson
            mak.redhat.com Marcos Entenza Garcia
            Penghao Wang Penghao Wang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 1 week
                1w
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 week
                1w