Feature Overview

HyperShift's concept can be considered an architectural paradigm shift compared to OpenShift's standalone model for delivering clusters, this shift raises an important question...What is the consumption model?

To get the idea, let's have a look at OpenShift's existing consumption models.

• Self-managed (local, on-prem, cloud) 
• Managed (OpenShift Dedicated, OpenShift on IBM Cloud, ROSA, ROKS,...)

With HyperShift, the consumption models will likely need to be adapted. This feature is there to track support for HyperShift with the different consumption models. 

Background, and strategic fit

There is really no product until there is a consumption model for it. It is important to give the same level of flexibility of choosing the best consumption model to our users. 

Goal(s)

Re-define and iterate over necessary support of HyperShift with existing consumption models.

HyperShift is meant to be consumed as Clusterware for SaaS providers. The goal of this feature is track support for HyperShift in existing providers (e.g. ROSA, ROKS, OSD, ....)