Goal
Define the HyperShift cluster lifecycle experience for 2.6. This story will focus on identifying the end to end workflows to support HyperShift hosted clusters once they have been created.

Background
Allow users to lifecycle HyperShift Hosted clusters on Hosting Service Clusters (destroy, upgrade, scale).

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.

Use cases

• As a Cluster Service Provider, I want to be able to view the Cluster Details page for a HyperShift Hosting Service cluster (identify the delta in details that HyperShift clusters need to surface)
• As a Cluster Service Provider, I want to be able to upgrade my HyperShift hosted clusters via my HyperShift Hosting Service cluster
• As a Cluster Service Provider, I want to be able to scale my HyperShift hosted cluster via my HyperShift Hosting Service cluster
• As a Cluster Service Provider, I want to be able to delete a HyperShift hosted cluster
• As a Cluster Service Provider, I want to be able to add a label to an existing cluster and convert it to a Hosting Service cluster

Requirements
[to come]

Deliverables
[to come]

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)