The new feature allowing users to disable the Grafana deployment needs to be documented.

MON-1675 added a new enabled field to the grafana section in the cluster-monitoring-config ConfigMap that configures CMO. Setting this to false will disable the Grafana deployment and cause the associated resources to be deleted from the cluster. Example ConfigMap that disables Grafana:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cluster-monitoring-config
  namespace: openshift-monitoring
data:
  config.yaml: |
    grafana:
      enabled: false

A few notes on this feature:

• Grafana is enabled by default on both new and existing clusters.
• Disabling Grafana will cause the following components to restart:
  • Platform (i.e. not user-workload) Prometheus (this means loss of previous metrics without persistent storage configured)
  • Thanos Querier
• The grafanaPublicURL field will disappear from the monitoring-shared-config ConfigMap in the openshift-config-managed namespace.
  • Note: These URLs in the ConfigMap are likely going away in 4.9 anyway. See: PR #1223