Value Statement

When showing Users and Groups in the UI, currently we are only showing Users/Groups on the hub cluster. However there is a valid scenario where a user may have logged into a managed cluster but not the hub. Therefor for displaying Users/Groups, we should get all Users/Groups from all clusters using search, pool them together, deduplicate, and display all of them. If a User or Group is on the hub and managed clusters, I would choose to display the hub version vs the managed cluster version, although they should be identical.

Definition of Done for Engineering Story Owner (Checklist)

• If userA or groupA exists on hub but on no other managed clusters, userA or groupA should show on the RBAC UI
• if userB or groupB exists in a single managed cluster, but not the hub, userB or groupB should show on the RBAC UI
• If userC or groupC exists on the hub and another managed cluster, UI should show userC or groupC details from the hub cluster (yaml, details, etc)

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.