From 678bec7f4caefd44e27b31452e9c50e378c3ed55 Mon Sep 17 00:00:00 2001 From: Eliska Romanova Date: Wed, 12 Feb 2025 09:37:22 +0100 Subject: [PATCH] OBSDOCS-1492: [DOC] Early validation for monitoring configmaps --- ...onfig-map-reference-for-the-cluster-monitoring-operator.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/observability/monitoring/config-map-reference-for-the-cluster-monitoring-operator.adoc b/observability/monitoring/config-map-reference-for-the-cluster-monitoring-operator.adoc index 4ee35e301ffd..b10eac377c1c 100644 --- a/observability/monitoring/config-map-reference-for-the-cluster-monitoring-operator.adoc +++ b/observability/monitoring/config-map-reference-for-the-cluster-monitoring-operator.adoc @@ -32,7 +32,7 @@ Only the parameters and fields listed in this reference are supported for config For more information about supported configurations, see xref:../monitoring/configuring-the-monitoring-stack.adoc#maintenance-and-support_configuring-the-monitoring-stack[Maintenance and support for monitoring]. * Configuring cluster monitoring is optional. * If a configuration does not exist or is empty, default values are used. -* If the configuration is invalid YAML data, the Cluster Monitoring Operator stops reconciling the resources and reports `Degraded=True` in the status conditions of the Operator. +* If the configuration has invalid YAML data, or if it contains unsupported or duplicated fields that bypassed early validation, the Cluster Monitoring Operator stops reconciling the resources and reports the `Degraded=True` status in the status conditions of the Operator. ==== == AdditionalAlertmanagerConfig