Merge pull request #88420 from eromanova97/OBSDOCS-1492a

[enterprise-4.17] Strict validation for monitoring configmaps

Author: xenolinux

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, the Cluster Monitoring Operator stops reconciling the resources and reports the `Degraded=True` status in the status conditions of the Operator. Starting with {product-title} 4.17.5, the validation criteria is improved. Upgrading the Cluster Monitoring Operator to version 4.18 or later is blocked if unsupported fields or invalid configurations are detected.
 ====
 
 == AdditionalAlertmanagerConfig