Epic Goal

Presently, in the current version of ACM/MCE, there isn’t a supported mechanism for customers to adjust or customize the deployments sizes. When customers manage a large number of clusters or have resource intensive applications, this often results in constraints on other resources, leading to out-of-memory (OOM) issues in their environment.

Develop sizing details for your deployments following the guidance created in the DDR associated with the parent feature.

Scenarios

Consider how to document sizing details for your deployments.

Consider how to validate sizes from documented details.

Acceptance Criteria

Sizes developed, documented and automated validation developed to show when sizes need to be reduced or increased as changes are made to the deployments.

Dependencies (internal and external)

Previous Work (Optional):

1. Use scalability data available from the performance team

Open questions:

DDR approval is not complete.

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.