-
Story
-
Resolution: Unresolved
-
Critical
-
Global Hub 1.4.0
-
3
-
False
-
None
-
False
-
-
-
GH Train-21 2
-
Critical
-
None
Epic Goal
- Fix some gaps we found during DP
- Discuss if we need to extend the migration to other resources
Why is this important?
...
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.
- depends on
-
ACM-15758 As a global hub engineer, I can know the klusterlet config is applied successfully so that I can update hubAcceptClient to false to trigger the migration
- New
-
ACM-14994 [DP]As a global hub user, I can see the existing kubeconfig can be added into klusterlet config automatically
- Review
- relates to
-
ACM-14991 [MultipleHubs] Cannot be triggered to switch hub when modify hubAcceptsClient to false
- Closed
-
ACM-14992 [MultipleHubs] Cannot delete the managed hub cluster from the existing hub cluster
- Closed
-
ACM-14993 Cannot modify hubAcceptsClient to false if auto-approval is enabled
- Closed
-
ACM-14793 Cannot switch hub due to many CSRs created
- Closed