-
Story
-
Resolution: Unresolved
-
Critical
-
Global Hub 1.5.0
-
BU Features
-
5
-
False
-
None
-
False
-
-
ACM-19028 - Managed Cluster Hub Migration (TP)
-
-
-
GH Train-26
-
Critical
-
None
Value Statement
That is first step to support live migration
Definition of Done for Engineering Story Owner (Checklist)
- register the migration cluster from one hub to another
- delete the cluster from the source hub cluster if the cluster is synced into the target hub in the database
- deploy the configuration of the cluster into the target hub cluster
- The registering and deploying conditions can be seen in the status
- The phase is migrating during the above stages
- and the test case to cover the above workflow
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 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.
- clones
-
ACM-18601 As a cluster admin, I can check the migration's initializing status
-
- Closed
-