From 3062ab3535b680a6044fcb4b37ab6ce2a7a055e7 Mon Sep 17 00:00:00 2001
From: Lennart Jern <lennart.jern@est.tech>
Date: Thu, 18 Sep 2025 08:31:51 +0000
Subject: [PATCH] Docs: Show MHC unhealthyNodeConditions example

The migration docs for v1.10 - v1.11 mentions the change to
the timeout field but the example doesn't show it. This
commit adds it to the example.

Signed-off-by: Lennart Jern <lennart.jern@est.tech>
---
 .../developer/providers/migrations/v1.10-to-v1.11.md   | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/docs/book/src/developer/providers/migrations/v1.10-to-v1.11.md b/docs/book/src/developer/providers/migrations/v1.10-to-v1.11.md
index b364e3a7d35d..012e3245df26 100644
--- a/docs/book/src/developer/providers/migrations/v1.10-to-v1.11.md
+++ b/docs/book/src/developer/providers/migrations/v1.10-to-v1.11.md
@@ -1125,7 +1125,10 @@ spec:
   clusterName: ""
   selector: { ... }
   nodeStartupTimeout: 300s
-  unhealthyConditions: { ... }
+  unhealthyConditions:
+    - type: ""
+      status: ""
+      timeout: 300s
   unhealthyRange: "[1-4]"
   maxUnhealthy: "80%"
   remediationTemplate:
@@ -1156,7 +1159,10 @@ spec:
   selector: { ... }
   checks:
     nodeStartupTimeoutSeconds: 300
-    unhealthyNodeConditions: [ ... ]
+    unhealthyNodeConditions:
+      - type: ""
+        status: ""
+        timeoutSeconds: 300
   remediation:
     triggerIf:
       unhealthyInRange: "[1-4]"