Value Statement

It was decided in the most recent architecture/engineering meeting that we will use Placement and PlacementDecision for cluster selection in the MulticlusterRoleAssignment controller. Here is a slack channel with the related discussion:

https://redhat-internal.slack.com/archives/GUWQE4D2N/p1756945745022279

Here are the basics of what was agreed upon:

1. MRA spec will have an array of clusters
2. MRA controller will create/delete Placements (manage them) for each role assignment
3. MRA controller will look at PlacementDecision to determine cluster lists and related clusters for each role assignment

It was decided in the above thread to introduce clusterSelection instead of supporting Placements. clusterSelection will allow us to support Placement easier if we decided to go with that in the future.

Definition of Done for Engineering Story Owner (Checklist)

• ...

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.