Value Statement

As we prepare to scale our components to support various hub cluster sizes, we need to thoroughly test the Discovery operator and document the resulting data from these tests.

We will simulate the Discovery component with 25 managed clusters and then 50 managed clusters. Additionally, we will test the operator's performance based on the number of supported discovered clusters.

Definition of Done for Engineering Story Owner (Checklist)

• [] Discovery operator tested with 25 managed clusters.
• [] Discovery operator tested with 50 managed clusters.
• [] Operator tested for performance and stability with 100 discovered clusters.
• [] Operator tested for performance and stability with 500 discovered clusters.
• [] Operator tested for performance and stability with 1000 discovered clusters.

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.