Epic Goal

Create an easier way to reattach managed clusters after hub api certificate change.

Why is this important?

Currently the only way to reconnect managed clusters after the hub cluster api certificate is changed is to detach/re-import which is cumbersome for larger environments and certificates are changed frequently (yearly).

Scenarios

Updating hub API cert causes managed clusters to lose connection and requires re-import.

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