Goal
Define the end to end user experience for ACM to provision a HyperShift hosted cluster. This story will focus on identifying the end to end workflows to support HyperShift tech preview for ACM 2.6.

Background
HyperShift is a deployment model that provides OpenShift clusters where the control-planes are externally managed on another cluster (that we call the "Hosting Service Cluster") as pods.

Personas to focus on

• Cluster Service Provider - the user hosting cluster control planes, responsible for up-time. UI for fleet wide alerts, configuring AWS account to host control planes in, user provisioned infra (host awareness of available compute), where to pull VMs from has cluster admin management
• Cluster Service Consumer - the user empowered to request control planes, request workers, and drive upgrades or modify externalized configuration.  Likely not empowered to manage or access cloud creds or infrastructure encryption keys.

Requirements

• Identify the ideal user experience to provision a HyperShift hosted cluster for ACM
• The workflow will begin something like:
  • At a high level the user will ask themselves if they want a managed or self-managed experience. In this case we are focused on the self-managed experience in ACM.
  • Once a user identifies they want a self-managed experience they will ask themselves do they want this service hosted or standalone? If the answer is hosted, that will trigger the HyperShift experience.
  • Once a Hosted HyperShift Cluster is selected, users will be prompted to select from a list of potential Hosting Service Clusters (also known as HUB clusters for the time being).
  • If no clusters are available to select to act as the Hosting Service Cluster, a user will be prompted to create one using the existing cluster creation flow in ACM today.
• We should work with Josh Packer on what the rest of that workflow will need to include once the Hosting Service Cluster has been selected.

Deliverables

• A miro board to outline the workflows to provision a HyperShift hosted cluster.
  • 01 - Happy path (a Hosting Service Cluster exists for the user select)
  • 02 - Where users need to create a Hosting Service Cluster and then can create the Hosted Cluster
  • 03 - There could be more we are not yet aware of or capturing here
• Mock ups to support the identified workflow

Resources

• UX Alignment doc | Miro
• HyperShift Overview & Outlook Deck
• HyperShift Consumption and Early Ops Options
• HyperShift + OpenShift Console Plan for GA
• Standalone HyperShift Consumption Through ACM - Deep-dive
• API availability

The HyperShift Taskforce (Contacts)

• PM: Scott Berens and Sho (ACM), Ali Mobrem (Console), Adel Zaalouk (HyperShift), Greg Sheremeta (OCM)
• UX:
  • Console: Megan
  • ACM/OCM: Matt Carleton, Lisa Lyman, Eric Fried
• ACM Backend: Joshua Packer
• Architects: Derek Carr (OpenShift)