Epic Goal

The goal of this epic is to enable cluster administrators to import existing MCE clusters hosting hosted control planes into a single ACM to consolidate a view of all hosting and hosted clusters. As cluster admins continue provisioning and de-provisioning hosted clusters in the managed MCE clusters, the HCs are auto-imported and auto-removed from the ACM hub cluster as well. 

The HCs will have two hub clusters in this scenario, ACM and MCE, and the cluster administrator has view-only access from ACM and view and manage access from MCE.

Why is this important?

This epic addresses frequent inquiries from customers and RH teams.

My customer is having below scenario:
Customer  is having multiple (more than 100) clusters on which they want to create VMs using openshift virtualization. Then, use HCP (Hosted control plane) to create cluster using VMs. For HCP, ACM HUB is a must.now, Since customer is having more than 100 ACMs where ACM HUB is needed (because of HCP), then will it be good solution to use ACM global hub to manage these many HUBs and  HUBs will manage clusters created using HCP (hosted control plane)?Also, is it possible to push policy/deploy app etc from global Hub to Hubs and their managed clusters?

IHAC (Intesa Sanpaolo Bank) with ACM already adopted for application deployment, observability and policies, not for cluster creation (they use UPI mode and custom automation).
They are now interested in HCP for bare metal (on prem) and possibly virtual (now TP) and the question is if HCP management cluster is required or suggested to be on the same ACM cluster or it could be decoupled from it (one ACM cluster and one separate HCP management cluster). Which are advantages/disadvantages of the two approaches if both are possible?

Scenarios

I start with one MCE to host hosted clusters. Then for a scalability, logical-separation or any other reason, I start having multiple MCEs to hosted hosted clusters. Then I start asking questions: Can a single ACM manage all these hosting and hosted clusters to enforce policies, manage applications.. etc?

1. Import MCEs into ACM.
2. All existing hosted cluster in MCEs are auto-imported into ACM when MCEs are imported.
3. New hosted clusters are provisions through MCE. They are auto-detected and auto-imported into ACM.
4. Hosted clusters are deleted through MCE. They are auto-detected and autor-removed from ACM.

Acceptance Criteria

• I can use ACM management tools like policies and application life-cycle on imported hosted clusters.
• I can view hosted clusters' cluster information from ACM such as node status, addon status.. etc.

Dependencies (internal and external)

1. https://issues.redhat.com/browse/ACM-8859 (server foundation)

Previous Work (Optional):

1. ...

Open questions:

1. ...

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.