Value Statement

When migrating a large number of managed clusters, doing so in a single batch can lead to performance bottlenecks and poor observability. To enhance scalability and control, we should support batch migration with optional canary rollout.

Definition of Done for Engineering Story Owner (Checklist)

• Migration controller can split selected clusters into configurable batch sizes.

• Each batch is processed sequentially or in parallel (configurable).

• Optional delay between batches to control load.

• Support a canary mode:

• • A small set of clusters (canary batch) are migrated first.

• • Subsequent batches proceed only if the canary succeeds.

• • Failures in canary batch halt the migration.

 
**

Notes:

• Batch metadata and progress should be visible in the UI and APIs.

• Canary logic should be toggleable and clearly logged.

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.