Epic Goal

1. Our goal is to help to create capacity & sizing recommendations for ACM.
2. Provide the agent footprint benchmark based on ACM 2.10.

Can follow the steps we did for ACM 2.9.

https://github.com/stolostron/acm-workload/blob/release-2.9/README.md 

https://github.com/stolostron/capacity-planning/pull/3 

      3. Given the feedback from microshift https://docs.google.com/presentation/d/1aR0GFHsJnLqH6X-MADBEw5PYmaWj6e5rBrQ2TLaEdRY/edit#slide=id.g2b6e447fadc_0_25 , we also need to run the test on microshift, since "an idle microshift cluster has a TOTAL utilisation of <200mcores", this is different from an ocp env, and we need to provide the data. (removed since the feedback is do not need to test on microshift )

Why is this important?

Customers need this type of capacity and sizing information as they embark on ACM deployments.

Scenarios

1. Existing (brown-field) set up: ACM hub is running with real clusters being managed under it    
2. No ACM running (green-field) but clusters that would be managed exists    
3. No ACM running (green-field) and clusters that would be managed do not exist  

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://github.com/stolostron/capacity-planning

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.