Goal 

Define common cluster inventory & lifecycle management patterns that can be shared across both managed (HAC+OCM) and on-premise (ACM+OCP) consoles built upon the Common Console Framework.

Why is this important?

As the line between our SaaS-based (OCM) and Software-based (ACM) cluster management offerings continues to blur, the experience of using a capability in one should be as familiar as possible when using the other in order to achieve a cohesive-feeling open hybrid cloud experience that doesn’t require re-learning.

Use cases

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) and new update paths 
• 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)

Out of scope

• Many of these things could (and probably should) be configured via policy-based governance by users in the future

Dependencies

• Need general agreement on the plan for cluster inventory architecture - ACM, MCE, open-cluster-management and KCP
• This may be outside of KCP’s focus area