Epic Goal

• RolloutManager controller needs to create a ServiceMonitor so that metrics from Rollouts will automatically be included in OpenShift monitoring.
• A service, argo-rollouts-metrics, is already created to provide access to metrics, it just needs to be connected to monitoring via a ServiceMonitor

Why is this important?

• Customers need to monitor components of the system including the Argo Rollouts which is deployed by the OpenShift GitOps Operator

Scenarios

1. Deploy Rollouts into a namespace with RolloutManager and be able to monitor Argo Rollouts

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Rollout metrics appear in Observe > Metrics in OpenShift console.

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