Feature Overview

Goals

Allow users to set the limits on memory and cpu for add-on components.

Provide a standard way for add-on developers to offer a way to set limits for add-on components.

Ensure customers have a simple, standardised way to set limits on all add-ons.

Ensure all new add-ons adhere to this standard.

Addons to utilise this structure:

• Submariner
• volsync
• observability
• search
• policy
• application
• hypershift
• global-hub
• cluster-proxy
• managed-serviceaccount

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases

Edge scenarios with very limited resources

Questions to answer

Out of Scope

Background, and strategic fit

Customers may need to manage the resource consumption on spokes for a majority of use cases.

One key is far edge: https://issues.redhat.com/browse/ACM-626

Assumptions

Should use the same key/value pairs for all add-ons
Goal is for it feel as "cut and paste equal” if possible.
Use same config structure.
Ensure a clean and easy UX experience that offers consistency across all add-ons.

Customer Considerations

Documentation Considerations

TBC

• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?