Epic Goal

We currently do not have a clear documentation on the resource footprint of each hypershift hosted control plane and how to plan compute capacity of ACM hub cluster to have desired number of hypershift hosted control planes. 

This epic is to come up with such documentation by tests and verifications. 

Why is this important?

This is important for ACM administrator to plan the compute capacity so that both ACM and hypershift hosted control planes do not run out of resources and become nonfunctional.

Scenarios

...

Acceptance Criteria

• Documentation on resource footprint of a single hosted control plane in SingleReplica mode
• Documentation on resource footprint of a single hosted control plane in HA mode
• Documentation on example compute capacity planning to run 10 hosted control planes on ACM hub cluster 

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

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 - Downstream documentation merged: <link to meaningful PR>