Epic Goal

As we enable addon agents to accept user configurable resource and limit settings (see https://issues.redhat.com/browse/ACM-12094 and https://issues.redhat.com/browse/ACM-15963) each agent team will need to review and update their agent as per https://github.com/stolostron/foundation-docs/blob/main/addon/addon-resource-requirements.md 

Why is this important?

Addons run in a variety of places and under vastly differently resources environments from far edge to large servers. Being able to manually adjust the resource and limits allows an admin to tune the agent to their environment and optimise the resources available. 

Currently adjusting limits on agents is temporary and is reset by the operator.

Scenarios

Anywhere agents are run

Acceptance Criteria

All agent offerings follow the standardised approach allowing users to adjust resources and limits in the same way.

The feature is fully documented for customers to follow with ease.

Dependencies (internal and external)

All agent subteams:

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

Previous Work (Optional):

Open questions:

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.
• Considerations were made for Extended Update Support (EUS)