Epic Goal

With the epic https://issues.redhat.com/browse/ACM-2252, we are able to initiate the cluster registration directly from agent. It opens the possibility that we can use this mechanism to let agent automatically switch from one hub to another. With that we do not need to the hub to trigger the agent switch with managedServiceAccount, and could easily to support hubs with active-active mode.

Why is this important?

This is important to support business continuity

Scenarios

• user can set the klusterlet to fetch bootstrap-hub-kubeconfig from multiple hubs via an endpoint provided in ACM-2252.
• klusterlet detects the healthiness of each hub, and switch the bootstrap-hub-kubeconfig when needed.
• klusterlet is able to connect to the switched hub and function well.

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://issues.redhat.com/browse/ACM-2252

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 - Downstream documentation merged: <link to meaningful PR>