Goal Summary:

The default ACS resource requirements are:

• too large for a typical dev cluster (wasteful for a toy workload, require tweaks to fit)
• too small for a demanding installation (source of support cases)

So users and developers alike need to tweaking them.

This is currently only possible on a very low level (individual CPU/RAM/disk changes for every single component). It's:

• tedious
• source of constant toil as the system evolves
• repeated by many people in many places in slightly different ways

This ticket calls for a coarse, high-level way to set resources, to avoid repetition and increase velocity.

Goals and expected user outcomes:

There is a configuration option to set resource requirements for all components at once, e.g. "big/small" or "high/low".

Acceptance Criteria:

A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.

<enter general Feature acceptance here>

Success Criteria or KPIs measured:

A list of specific, measurable criteria that will be used to determine if the feature is successful. Include key performance indicators (KPIs) or other metrics., etc. Initial completion during Refinement status.

<enter success criteria and/or KPIs here>

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios together with user type/persona. Initial completion during Refinement status.

<your text here>

Out of Scope (Optional):

High-level list of items that are out of scope. Initial completion during Refinement status.

<your text here>