Value Statement

In small foot print user scenarios, having 4 clusters (one active, one passive hub and 2 ManagedClusters for workloads) seems excessive in terms of required resources. To reduce such footprints, support hosting an ACM hub on a ManagedCluster, and similarly hosting a passive instance on another ManagedCluster, reducing the foot print to 2 clusters for such users.

The hub in this instance is used for cluster, application, and policy management of the cluster that is hosting the hub. Similarly the passive hub is a ManagedCluster that has application and policy based management ongoing from the active hub.

Currently using an existing ManagedCluster as the passive hub can/will conflict with the usage of "local" ManagedCluster resources as the active hub is named/used. This prevents the desired use-case detailed in this story from being a reality.

A active hub that is "demoted" and migrated to the passive hub, needs required resource cleanup to prepare it as a new passive hub for future recovery/restore. The "local" hub name potentially would conflict with this requirement.

The ask in the story hence is to support a ManagedCluster as an active or a passive hub, with the ability to reuse the older active hub (post recovery) as a future passive hub.

NOTE: A ManagedCluster as a hub that has user deployed resource (like application subscriptions or gitops) would require cleanup outside the scope of hub cleanup of the older active hub. Automating this is not expected as part of this request. The key item would be promoting an ManagedCluster from a passive hub to an active hub or as a target of hub restore.

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 template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

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