Skip to content

Commit a811b50

Browse files
committed
OBSDOCS-405-document-new-monitoring-plugin
1 parent c10b633 commit a811b50

File tree

1 file changed

+12
-2
lines changed

1 file changed

+12
-2
lines changed

modules/infrastructure-moving-monitoring.adoc

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88

99
The monitoring stack includes multiple components, including Prometheus, Thanos Querier, and Alertmanager.
1010
The Cluster Monitoring Operator manages this stack. To redeploy the monitoring stack to infrastructure nodes, you can create and apply a custom config map.
11-
11+
1212
.Procedure
1313

1414
. Edit the `cluster-monitoring-config` config map and change the `nodeSelector` to use the `infra` label:
@@ -107,8 +107,18 @@ data:
107107
- key: node-role.kubernetes.io/infra
108108
value: reserved
109109
effect: NoExecute
110+
monitoringPlugin:
111+
nodeSelector:
112+
node-role.kubernetes.io/infra: ""
113+
tolerations:
114+
- key: node-role.kubernetes.io/infra
115+
value: reserved
116+
effect: NoSchedule
117+
- key: node-role.kubernetes.io/infra
118+
value: reserved
119+
effect: NoExecute
110120
----
111-
<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.
121+
<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.
112122

113123
. Watch the monitoring pods move to the new machines:
114124
+

0 commit comments

Comments
 (0)