Epic Goal

The Operator sets up each ArgoCD instance to be scraped by OpenShift cluster monitoring (by creating ServiceMonitors and labeling the namespace with openshift.io/cluster-monitoring=true), without the possibility to opt-out.

We need to make this optional on a per-instance basis.

Why is this important?

For customers with a lot of ArgoCD instances, the scraped metrics result in a huge amount of storage being used, and it provides very little to no value to them.

See https://issues.redhat.com/browse/RFE-3120 for more details.

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• Each ArgoCD instance can opt-out of automated scraping
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Make sure the changes are backward compatible and does not any existing customers.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment