Merge pull request #63922 from bburt-rh/OBSDOCS-405-document-new-monitoring-plugin

OBSDOCS-405: document-new-monitoring-plugin-in-moving-components-to-infra-nodes

Author: bburt-rh

modules/infrastructure-moving-monitoring.adoc

@@ -8,7 +8,7 @@
 
 The monitoring stack includes multiple components, including Prometheus, Thanos Querier, and Alertmanager.
 The Cluster Monitoring Operator manages this stack. To redeploy the monitoring stack to infrastructure nodes, you can create and apply a custom config map.
- 
+
 .Procedure
 
 . Edit the `cluster-monitoring-config` config map and change the `nodeSelector` to use the `infra` label:
@@ -107,8 +107,18 @@ data:
       - key: node-role.kubernetes.io/infra
         value: reserved
         effect: NoExecute
+    monitoringPlugin:
+      nodeSelector:
+        node-role.kubernetes.io/infra: ""
+      tolerations:
+      - key: node-role.kubernetes.io/infra
+        value: reserved
+        effect: NoSchedule
+      - key: node-role.kubernetes.io/infra
+        value: reserved
+        effect: NoExecute
 ----
-<1> Add a `nodeSelector` parameter with the appropriate value to the component you want to move. You can use a `nodeSelector` in the format shown or use `<key>: <value>` pairs, based on the value specified for the node.  If you added a taint to the infrasructure node, also add a matching toleration.
+<1> Add a `nodeSelector` parameter with the appropriate value to the component you want to move. You can use a `nodeSelector` in the format shown or use `<key>: <value>` pairs, based on the value specified for the node. If you added a taint to the infrastructure node, also add a matching toleration.
 
 . Watch the monitoring pods move to the new machines:
 +