Goal

Define a common cluster inventory + lifecycle management patterns and reusable components that will power both managed(HAC + OCM) and on-premise solutions(ACM).

Why is this important?

As the capability differences between what Red Hat offers as SaaS and Software continue to blur.

As an administrator, I need to:

• Customize the columns of my cluster inventory list view (e.g. remove Subscription information if I don’t care about it)
• When applicable, launch a cluster’s local console experience
• Set a display name for my clusters (see OCM)
• Import clusters from other providers (see ACM)
• Register clusters that may be air-gapped (see OCM)
• Detach clusters without destroying them (see OCM/ACM)
• Destroy clusters (see OCM/ACM)
• Update clusters (see OCM/ACM)
• Hibernate clusters (see OCM/ACM)
• Manage cluster MachinePools (see OCM/ACM)
• Archive missing clusters (see OCM)
• Apply IDP configuration to a cluster (see OCM, may relate to CIAM)
• View cost information related to a cluster (see OCM Cost Management integration)
• View and create Red Hat support cases related to managed clusters (see OCM)
• View a history of significant actions that Red Hat SRE has taken on managed clusters (see OCM)
• See clusters that SaaS/c.rh.c knows about that aren’t in my on-prem list (see ACM’s discovered clusters)
• Add clusters to an environment (see HAC-###)

Requirments

• Clusters with & without the Console operator installed (e.g. no “Open Console” button, also what is that ‘Console”)- There shouldn't be any different.
• Connected clusters - able to view live-updating streaming data straight from the cluster (e.g. metrics charts, alerts, activity card), new clusters created in HAC/KCP will be able to do this
• Slowly-connected clusters - getting data from telemetry every 30 minute or whatever (e.g. no fancy live-updating data)
• Disconnected clusters - barely any data, more for subscription tracking purposes
• Other clusters may be created in this new HAC experience and are sending live data where we can show more info for infra management directly in the cloud

Acceptance criteria

• List page includes at least all information available in OCM and ACM today (default columns may be different)
• A list of clusters that make up an Environment (likely within an Environment’s Details page)

Deliverables 

• Final design with mocks and descriptions

• Acceptance from stakeholders

Related links

• Ali’s brainstorming of columns and actions in a combined view
• Multicluster engine for Kubernetes operator
• Proposal to add Labs App (show me how to update from where I am to the latest):
• WIP Doc: Proposal to move the Labs application functionality into OCM

Marvel mockups:

https://marvelapp.com/prototype/h75bd5e/screen/82919014 

Slide deck: 

https://docs.google.com/presentation/d/1PFXMarjNqQxvicuPjtPPPhz6V-dgkrzOczspaphHKnA/edit#slide=id.gf8d14cb78d_0_0