Value Statement

Once a ROSA cluster is provisioned, the customer may

• Case 1: Import it as a managed cluster to a customer ACM/MCE hub;
• Case 2: Install ACM/MCE on this cluster and enable the local-cluster;

Considering the cluster has already joined the SD hub running on the service cluster, we need to verify if the above cases are supported and capture the following information in a doc.

We need to change the namespace used by OCM/SD for HostedMode.
We should state that we then support ACM management of ROSA-Hosted Control Plane Clusters (and any caveats we might have)
We should state you can install MCE on a ROSA-Hosted Control Plane cluster and we need to include whether they can or can not have local-cluster active, which dictates whether they can use this as a Hosting Cluster for more HCP
We should state you can install ACM on a ROSA-HCP cluster and whether local-cluster is supported.

In addition, automation test cases are required to make sure the supported cases will not be broken by any future code change.

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.