From 1d89e637b9778d0a83053ec323162406a0d53cf2 Mon Sep 17 00:00:00 2001 From: Naga Ravi Chaitanya Elluri Date: Thu, 23 Jul 2026 22:46:33 -0400 Subject: [PATCH] Update NodeHealthCheck minHealthy guidance for hyperconverged storage Signed-off-by: Naga Ravi Chaitanya Elluri --- modules/virt-configuring-node-health-checks-for-vms.adoc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/modules/virt-configuring-node-health-checks-for-vms.adoc b/modules/virt-configuring-node-health-checks-for-vms.adoc index fe13642ea92a..8b6626e1d2f3 100644 --- a/modules/virt-configuring-node-health-checks-for-vms.adoc +++ b/modules/virt-configuring-node-health-checks-for-vms.adoc @@ -25,7 +25,7 @@ kind: NodeHealthCheck metadata: name: nodehealthcheck-sample spec: - minHealthy: 1 + minHealthy: pauseRequests: - remediationTemplate: @@ -56,7 +56,9 @@ spec: + where: + -* `spec.minHealthy` defines the number of worker nodes required to host VMs that migrate from failed nodes. For critical environments, set this value to the minimum number of nodes that you require to maintain the cluster workload. +* `spec.minHealthy` defines the number of worker nodes required to host VMs that migrate from failed nodes. +** For critical environments, set this value to the minimum number of nodes that you require to maintain the cluster workload. +** For hyperconverged storage, set this value to one less than your number of nodes to limit remediation to a single worker-node failure and maintain storage stability. * `spec.remediationTemplate` defines the remediation template to use when the Node Health Check Operator detects an unhealthy node. This example uses the Self Node Remediation Operator. * `spec.escalatingRemediations` defines escalating remediation strategies. If the initial remediation does not resolve the issue within the specified timeout, the next remediation strategy runs. * `spec.selector` defines the nodes to monitor. This example monitors all worker nodes.