Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-519

Unify and Instrument Hosted Control Planes Storage Operators

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • XCMSTRAT-276(P0) ROSA HCP Critical Features + Bugs
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • 0

      Feature Overview (aka. Goal Summary)  

      Unify and update hosted control planes storage operators so that they have similar code patterns and can run properly in both standalone OCP and HyperShift's control plane.

      Goals (aka. expected user outcomes)

      • Simplify the operators with a unified code pattern
      • Expose metrics from control-plane components
      • Use proper RBACs in the guest cluster
      • Scale the pods according to HostedControlPlane's AvailabilityPolicy
      • Add proper node selector and pod affinity for mgmt cluster pods

      Requirements (aka. Acceptance Criteria):

      • OCP regression tests work in both standalone OCP and HyperShift
      • Code in the operators looks the same
      • Metrics from control-plane components are exposed
      • Proper RBACs are used in the guest cluster
      • Pods scale according to HostedControlPlane's AvailabilityPolicy
      • Proper node selector and pod affinity is added for mgmt cluster pods

       

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

       

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

       

      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.

       

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

       

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

       

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

       

      Interoperability Considerations

      Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

            rh-gs-gcharot Gregory Charot
            azaalouk Adel Zaalouk
            Wei Sun Wei Sun
            Stephanie Stout Stephanie Stout
            Hemant Kumar Hemant Kumar
            Gregory Charot Gregory Charot
            Dave Mulford Dave Mulford
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: