Value Statement

Fine Grained RBAC is a Tech Preview - therefore we will have to feature gate this. As is the custom we will add this in MCH CR (as is the custom for other Tech Previews).

Typically - 

 - configOverrides: {} 
   enabled: true 
   name: fine-grained-rbac-preview

If a customer has issues with the Tech Preview, then can disable this. All we will need is for Search and UI RBAC calls to fall back to existing code.

Definition of Done for Engineering Story Owner (Checklist)

• This is disabled and Search/UI works as usual
• When this is enabled Console will add the RBAC UI and Aggregate API Server will start the computation etc.
• When this is enabled, Search/UI will make calls to new RBAC
• When this is rolled back - the Console UI removes the new RBAC UI, RBAC calls works the old way. 
• What will happen to the clusterpermissions that are rolled out?

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.