Value Statement

As a user preparing a large-scale migration,
I want to select managed clusters using labels or placements in the Migration spec,
So that I don't have to hardcode cluster names and can support flexible, large-scale migrations.

Definition of Done for Engineering Story Owner (Checklist)

• Migration CR supports spec.placement and/or spec.selector fields to dynamically select managed clusters.

• The spec.includeManagedClusters field remains supported but becomes optional if selector/placement is used.

• Placement decisions are evaluated prior to migration execution and produce a resolved cluster list.

• Label selector supports Kubernetes-style syntax (e.g., matchLabels, matchExpressions).

• Batch migration strategy is considered and supports grouping clusters for staged rollouts (e.g., batch size or group ID).

• Validation fails gracefully if selector or placement results in zero matched clusters.

• CRD and documentation are updated with examples of cluster selection using labels or placements.

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](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

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.