-
Story
-
Resolution: Done
-
Critical
-
Global Hub 1.4.0
-
3
-
False
-
None
-
False
-
-
-
GH Train-21 2
-
Critical
-
None
Value Statement
- Fix some gaps we found during DP
Definition of Done for Engineering Story Owner (Checklist)
* split 2 stage for migration: 1. apply klusterletconfig to the managedcluster. 2. modify hubAcceptClient to false to trigger migration
* transfer the klusterletAddonConfig to the target cluster
*
Development Complete
* The code is complete.
* Functionality is working.
* Any required downstream Docker file changes are made.
Tests Automated
* [x] Unit/function tests have been automated and incorporated into the
build.
* [x] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
* [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
* [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
* Call out this sentence as it's own action:
* [ ] Link the development issue to the doc issue.
Support Readiness
* [ ] The must-gather script has been updated.
- depends on
-
ACM-14994 [DP]As a global hub user, I can see the existing kubeconfig can be added into klusterlet config automatically
-
- Closed
-
- relates to
-
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-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
-