From f8d17a4aca6ca1e4578cbae394c9d75752fc4233 Mon Sep 17 00:00:00 2001 From: Carlo Lobrano Date: Tue, 12 Mar 2024 16:39:52 +0100 Subject: [PATCH] Minor typo fix Signed-off-by: Carlo Lobrano --- recover_affected_workloads.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recover_affected_workloads.md b/recover_affected_workloads.md index c4652da..0ded790 100644 --- a/recover_affected_workloads.md +++ b/recover_affected_workloads.md @@ -47,7 +47,7 @@ the volume from the underlying storage system - a unique operation per driver pr After a successful unpublishing the pod and the volume can start again, on a different node. -## Virtualized worker note +## Virtualized worker node Nodes which are VMs should be configured with a watchdog device ([see libvirt's watchdog support][3]) In case it's not configured then self-node-remediation fallbacks to rebooting the machine using 'systemctl reboot'. The benefits of a virtualized watchdog is that its running