From 42d7de5195743db2014c9e5f332bf26bbd850aa4 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Thu, 24 Oct 2024 14:47:27 -0400 Subject: [PATCH] MCO add links to runbooks --- modules/machine-config-node-drain.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/modules/machine-config-node-drain.adoc b/modules/machine-config-node-drain.adoc index 7a9b8726d5..401560f129 100644 --- a/modules/machine-config-node-drain.adoc +++ b/modules/machine-config-node-drain.adoc @@ -18,6 +18,11 @@ After you make the changes, the MCO generates a new rendered machine config. In Throughout this process, the MCO maintains the required number of pods based on the `MaxUnavailable` value set in the machine config pool. +[NOTE] +==== +There are conditions which can prevent the MCO from draining a node. If the MCO fails to drain a node, the Operator will be unable to reboot the node, preventing any changes made to the node through a machine config. For more information and mitigation steps, see the link:https://github.com/openshift/runbooks/blob/master/alerts/machine-config-operator/MachineConfigControllerDrainError.md[MCCDrainError] runbook. +==== + If the MCO drains pods on the master node, note the following conditions: * In {sno} clusters, the MCO skips the drain operation.