Value Statement

Enhance ClusterPermission to provide warnings if user/group/role/ClusterRole do NOT exist on the ManagedCluster

DDR : https://docs.google.com/document/d/17TG-chlFWlFKznWmLuY591OZgbffb1ehdsVZ3vwQmv0/edit?tab=t.0

We decided to only validate Role/ClusterRole because of cluster proxy impersonation, the user doesn't need to exist on the managed cluster to work.

https://redhat-internal.slack.com/archives/C08HJNGCUUC/p1749132449539019

https://redhat-internal.slack.com/archives/C08HJNGCUUC/p1749138540259299

https://redhat-internal.slack.com/archives/C08HJNGCUUC/p1749138547665669

Definition of Done for Engineering Story Owner (Checklist)

• Role/ClusterRole can be validated

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.