Goal
Define the cluster lifecycle experience for ROSA HyperShift hosted clusters in HAC Infra / OCM.

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.

Terminology

• Hosting Service Cluster - An OpenShift cluster which hosts HyperShift and zero to many Hosted Clusters.
• Hosted Cluster - An OpenShift API endpoint managed by HyperShift.

Use cases

• Identify the different uses cases as a Cluster Service Provider and Cluster Service Consumer. For example:
  • As a Cluster Service Provider, I want to be able to view the Cluster Details page for a HyperShift Hosted Cluster (identify the deltas in the details page for the hosted cluster vs classic cluster)
  • As a Cluster Service Provider, I want to be able to upgrade my HyperShift hosted clusters.
  • As a Cluster Service Provider, I want to be able to scale my HyperShift hosted cluster.
  • As a Cluster Service Provider, I want to be able to delete a HyperShift hosted cluster.

Requirements

• Identify the deltas in user experience for lifecyling ROSA HyperShift hosted clusters. For example, when I have a classic cluster, I can CRUD machinepools. When I have a hypershift cluster, instead I can CRUD nodepools.

Deliverables

• High level workflows
• Mock ups to support the identified workflows

Resources

• Supporting HyperShift Clusters in OCP
• HyperShift E2E Designs for ACM (WIP)
• 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: Matt Carleton, Lisa Lyman, Eric Fried
  • HAC Infra: Thi Le
• ACM Backend: Joshua Packer
• Architects: Derek Carr (OpenShift)

Of note: There were recent changes to the ROSA HyperShift GA plan. Customers will now have a topology choice, classic OR hypershift. See the full slack thread here: https://coreos.slack.com/archives/C02LM9FABFW/p1647894453234299