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

HyperShift Core Component Readiness for GA - Part II

XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 0% To Do, 0% In Progress, 100% Done
    • 0

      Feature Overview

      HyperShift is used as a backend for provisoning OpenShift clusters with Hosted control planes. It can be consumed via two management models: 

      • Managed for cloud services (ROSA/ARO/...): Where HyperShift is used as a backend. 
      • Self-managed via MCE/ACM: Where HyperShift is used directly to provide control-plane as a service. 

      Previously, we have been working on making sure HyperShift core code/component is ready/stable/resilient enough to be consumed in GA, the details of the precursor work are here. 

      Goals

      The goal of this Epic is to continue the effort and make sure HyperShift is primed for GA consumption. This includes but is not limited to: 

      • Ensure tools for data collection exist for support cases. 
      • Resources (requests/limits) are well configured (based on input from Chaos tests). 
      • HyperShift has a consistent cluster profile that can distinguish it as a form factor
      • Other stability/CI/e2e tests

              azaalouk Adel Zaalouk
              azaalouk Adel Zaalouk
              Alberto Garcia Lamela, Angus Thomas, Nicholas Stielau
              Stephanie Stout Stephanie Stout
              Alberto Garcia Lamela Alberto Garcia Lamela
              Dave Mulford Dave Mulford
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: