Value Statement

I would consider these test scenarios

1. Env with large # of clusters (2500)
2. 2500+ ClusterPermissions (MRA maintains one ClusterPermission per clusters)
3. Large number of namespaces (should come as part of the # of cluster since each one has it's own namespace ~ 2500)
4. Large number of ManagedClusterAddons (usually 8 per managed cluster so ~20000)

Create the ClusterPermissions using CLI and monitor the CPU and memory usage from the OCP metrics page and make sure they are within the limits. Investigate any OOMKilled issues with the controller pod. If large environments are not available we can simulate it by creating dummy data ie. just create the resources that are watched by the ClusterPermission controller.

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.