-
Story
-
Resolution: Done
-
Major
-
Global Hub 1.6.0
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
-
-
-
GH Train-32
-
None
Value Statement
Ensure the issue title clearly reflects the value of this user story to the
intended persona. (Explain the "WHY")
Definition of Done for Engineering Story Owner (Checklist)
- Need to validate the placement to ensure the placement is ready for use.
- Need to parse the placementDecision to get the managed clusters from the source cluster and pass it to the global hub cluster.
- Need to create a configmap to persist the managed clusters the migration takes. Because the placement decision is kept updated.
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:
- [x] Link the development issue to the doc issue. https://issues.redhat.com/browse/ACM-24676
Support Readiness
[ ] The must-gather script has been updated.
- clones
-
ACM-23319 As a cluster admin, I can be able to set placement name in migration cr
-
- Closed
-
- is cloned by
-
ACM-23323 As a cluster admin, I can be able to see all migration clusters in configmap
-
- Closed
-
- relates to
-
ACM-18341 As a cluster admin, I can batch migrate clusters from one hub to another using fuzzy matching
-
- Closed
-