You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RolloutManager controller needs to create a ServiceMonitor so that metrics from Rollouts will automatically included in Prometheus gathered metrics, including in OpenShift monitoring (for OpenShift users)
A service, argo-rollouts-metrics, is already created to provide access to metrics, it just needs to be connected to monitoring via a ServiceMonitor CR.
Why is this important?
Customers need to monitor components of the system including the Argo Rollouts which is deployed by the GitOps Operator
Scenarios
Deploy Rollouts into a namespace with RolloutManager and be able to monitor Argo Rollouts
jgwest
changed the title
RolloutManager should create a ServiceMonitor for users on OpenShift
RolloutManager should create a ServiceMonitor for users with ServiceMonitor support
Mar 14, 2024
RolloutManager controller needs to create a ServiceMonitor so that metrics from Rollouts will automatically included in Prometheus gathered metrics, including in OpenShift monitoring (for OpenShift users)
Why is this important?
Scenarios
(Originally a feature request from https://issues.redhat.com/browse/GITOPS-3271)
Work Criteria
RolloutsManager
CR is reconciled, it should create the corresponding ServiceMonitor CRThis should only occur when we detect that the cluster is an OpenShift clusterFor example, by checking the API version or looking for an OpenShift-only CR (e.g.Routes
)The text was updated successfully, but these errors were encountered: