Feature Overview

HyperShift can be considered as a middleware that provides OpenShift, clusters for different *Hyper*scalers. The end-product for HyperShift is an OpenShift cluster with externally managed control-planes, and hyper-distributed data-planes across different providers (e.g., AWS, GCP, Azure, Baremetal, ...).

This feature tracks the implementation of HyperShift's infrastructure backend for the different providers.

Background, and strategic fit

HyperShift is a design-pattern, not a new offering, the portfolio that Red Hat provides already with OpenShift did not change, e.g., self-managed support on the different cloud providers.

Providing choice on where users run their workloads (as already being done today) is important for providing the same level of UX.

Goal(s)

Covering the existing cloud-provider support matrix will likely span multiple releases. The goal of this feature is to track progress for bringing HyperShift support to the various cloud-providers.

Below is a rough order of planned provider support:

Provider Status

• AWS (TP/Done) - Used for ROSA and for self-managed hosted control planes
• Baremetal (via the Assisted Installer agent workflow) - Preview
• OCP Virt (Preview)
• Azure (Preview)
• vSphere (not in scope for CY 2022) 
• GCP (not in scope for CY 2022)

Some important questions that need to be answered: 

• How will the implementation of cloud-provider be handled in the control-plane? 
• Do we need to implement a Kubernetes cloud-provider for Node, Loadbalancers, routes, services?
• Can the Management cluster and the workload cluster have different providers?

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content Strategy.
• What concepts do customers need to understand to be successful in [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or Release Note)?