-
Story
-
Resolution: Done
-
Major
-
OpenShift 4.14 Freeze, OpenShift 4.10 Async, OpenShift 4.11 Async, OpenShift 4.12 Async, OpenShift 4.13 Async
-
8
-
False
-
-
False
-
-
-
OBSDOCS (June 20-July 10) #238, OBSDOCS (July 10-31) #239
Explicitly document how to enable dedicated Service Monitors
Currently, this is only documented within the configmap reference:
https://docs.openshift.com/container-platform/4.12/monitoring/config-map-reference-for-the-cluster-monitoring-operator.html#dedicatedservicemonitors
However, we must provide a working example, such as:
apiVersion: v1
kind: ConfigMap
metadata:
name: cluster-monitoring-config
namespace: openshift-monitoring
data:
config.yaml: |
k8sPrometheusAdapter:
dedicatedServiceMonitors:
enabled: true
And we also have to add some background about the feature: https://access.redhat.com/solutions/7012719
Otherwise, it is going to be too confusing for our customers
- duplicates
-
OBSDOCS-64 Improve prometheus-adapter consistency
- Closed
-
OBSDOCS-66 4.11 & 4.10 backport: Improve prometheus-adapter consistency
- Closed
- links to
(3 links to)
There are no Sub-Tasks for this issue.