Document URL: * Configuring the monitoring stack [https://docs.openshift.com/container-platform/4.1/monitoring/cluster-monitoring/configuring-the-monitoring-stack.html] Section Number and Name: * Configuring the cluster monitoring stack [https://docs.openshift.com/container-platform/4.1/monitoring/cluster-monitoring/configuring-the-monitoring-stack.html#configuring-the-cluster-monitoring-stack_configuring-monitoring] Describe the issue: Automatically restarted related pods(prometheus, alertmanager) after "cluster-monitoring-config" configmap is changed for configuration monitoring stack. But this behavior does not be mentioned on the documentation. When user delete or restart the pod immediately after modifying configmap, then useless restart can happen again by timing. It can look like unknown restart/issue to users. Suggestions for improvement: Add information such like, "If you change the config, then the related pods will start again for changes, so you need not to restart them manually." for suppressing misunderstanding. Additional information: This issue is also valid on v3.11 either.