Epic Goal

As part of the initiative to optimize hub size scaling configurations (default, small, medium, large, and xlarge), each squad must update the documentation to reflect the appropriate sizing details for their components. These details will aid in determining scaling behavior based on various cluster environments and variables like the number of resources or managed clusters.

Why is this important?

• Standardize hub size scaling configurations across all squads.
• Establish a foundation for ongoing performance tuning and adjustments.

Scenarios

...

Acceptance Criteria

• Each squad has identified the key variables that impact their component's performance based on the size of the cluster (e.g., number of resources, managed clusters).
• Documentation for each component has been updated to reflect these variables, including the sizing estimates for hub configurations (default, small, medium, large, and xlarge).

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 - 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.