Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Major
Fix Version/s: OpenShift 4.14 Freeze, OpenShift 4.10 Async, OpenShift 4.11 Async, OpenShift 4.12 Async, OpenShift 4.13 Async
Affects Version/s: OpenShift 4.14 Freeze, OpenShift 4.10 Async, OpenShift 4.11 Async, OpenShift 4.12 Async, OpenShift 4.13 Async
Component/s: Monitoring
Labels:
- customer
- must-have
- rfe

Story Points:
8
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Intelligence Requested:
Market:

Sprint:
OBSDOCS (June 20-July 10) #238, OBSDOCS (July 10-31) #239

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

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