-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
COO 0.4.0
-
None
-
False
-
-
False
-
-
The docs curerntly state:
The COO components function independently of the default in-cluster monitoring stack, which is deployed and managed by the Cluster Monitoring Operator (CMO). Monitoring stacks deployed by the two Operators do not conflict.
how is this achived?
how can I reuse objects such as serviceMonitors and PrometheusRule objects previously configured against the core or user workload instances?
- by changing the API from `servicemonitors.monitoring.coreos` -> `servicemonitors.monitoring.rhobs`