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

Refactor AWS EBS CSI driver operators to support hypershift



    • Refactor AWS EBS CSI driver operators to support hypershift
    • 6
    • False
    • None
    • False
    • Green
    • To Do
    • OCPSTRAT-519 - Unify and Instrument Hosted Control Planes Storage Operators
    • OCPSTRAT-519Unify and Instrument Hosted Control Planes Storage Operators
    • 100
    • 100% 100%


      Epic Goal*

      Our current design of EBS driver operator to support Hypershift does not scale well to other drivers. Existing design will lead to more code duplication between driver operators and possibility of errors.
      Why is this important? (mandatory)

      An improved design will allow more storage drivers and their operators to be added to hypershift without requiring significant changes in the code internals.
      Scenarios (mandatory) 

      Dependencies (internal and external) (mandatory)

      What items must be delivered by other teams/groups to enable delivery of this epic. 

      Contributing Teams(and contacts) (mandatory) 

      Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

      • Development - 
      • Documentation -
      • QE - 
      • PX - 
      • Others -

      Acceptance Criteria (optional)

      Provide some (testable) examples of how we will know if we have achieved the epic goal.  

      Drawbacks or Risk (optional)

      Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

      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” 




            rhn-engineering-jsafrane Jan Safranek
            hekumar@redhat.com Hemant Kumar
            Rohit Patil Rohit Patil
            0 Vote for this issue
            5 Start watching this issue



              Time Tracking

                Original Estimate - 6 weeks
                Time Not Required
                Not Specified