Epic Goal

• Add support for prometheus in agent mode in CMO

Why is this important?

• Reduced resource usage in case no local querying (that includes alerting) is needed.

Scenarios

1. User who export metrics to and query from external storage
2. Maybe in some multi cluster use cases?

Acceptance Criteria

• CMO can be configured to deploy prometheus in agent mode.
• Query requirements of local cluster on prometheus are mitigated, e.g. prometheus-adapeter, console, alerts
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents

Dependencies (internal and external)

1. Upstream support in prometheus operator https://issues.redhat.com/browse/MON-2178 

Previous Work (Optional):

1. …

Open questions::

1. Who to mitigate components that rely on local queries

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 - Downstream documentation merged: <link to meaningful PR>