From 7d3ef9cdb7452e6d6852e3132efd3ae0edbb7d2f Mon Sep 17 00:00:00 2001 From: Brian Burt Date: Thu, 24 Aug 2023 14:55:59 -0400 Subject: [PATCH] OBSDOCS-405-document-new-monitoring-plugin --- modules/infrastructure-moving-monitoring.adoc | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/modules/infrastructure-moving-monitoring.adoc b/modules/infrastructure-moving-monitoring.adoc index 13273b9b8e9a..c329cfb021be 100644 --- a/modules/infrastructure-moving-monitoring.adoc +++ b/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 `: ` 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 `: ` 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: +