Value Statement

In MulticlusterRoleAssignment for 2.15, cluster selection was done in each role assignment with "clusterSelection.type: clusterNames". For 2.16 GA, we are to remove/convert this functionality to "clusterSelection.type: placements". Spec is to look like this:

spec:
  subject:
    kind: User
    name: mshort55
  roleAssignments:
  - clusterRole: kubevirt.io:admin
    clusterSelection:
      type: placements
      placements:
      - name: placement1
        namespace: ns1
    name: kubevirt.io:admin-0788e62497285bf4 

Watch functionality for Placement and/or PlacementDecision will be implemented in another story.

Definition of Done for Engineering Story Owner (Checklist)

• clusterSelection.type: clusterNames is fully removed
• clusterSelection.type: placements is implemented and checks PlacementDecision for target clusters
• e2e tests added for new Placement functionality

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.