Epic Goal

Support migrating the managed clusters from one hub to another. the hub cluster can be different version of ACM and Openshift

Why is this important?

Customer's requirements. Will link the RFE or feature soon.

Scenarios

1. As a cluster admin, I will be able to migrate SNO clusters from one hub to another with the same version so that the SNO clusters can be managed by the new hub.
2. As a cluster admin, I will be able to migrate the SNO cluster from one hub to another (they are different versions both ACM and OpenShift) so that the SNO clusters can be managed by the new hub.
3. As a cluster admin, I will be able to migrate the observability metrics historical data from one hub to another for SNO clusters so that I can continue tracing the SNO clusters metrics via the new hub cluster.

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

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.
• Considerations were made for Extended Update Support (EUS)