-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
Global hub HA
-
Product / Portfolio Work
-
False
-
-
False
-
Not Selected
-
Done
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
How to support active and passive for global hub
Why is this important?
for the customer case, when they migrate all the managed clusters from an old ACM hub cluster, they want to have global hub in the new hub ready for use.
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
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)