add unhealthyConditions for machineDeployments to fit CAPI core 1.7.2

Signed-off-by: Runyu Zheng <[email protected]>
k3s-io · Jun 5, 2024 · de4cfba · de4cfba
1 parent 888216c
commit de4cfba
Showing 1 changed file with 4 additions and 1 deletion.
diff --git a/test/e2e/data/infrastructure-docker/clusterclass-k3s.yaml b/test/e2e/data/infrastructure-docker/clusterclass-k3s.yaml
@@ -40,7 +40,10 @@ spec:
               name: k3s-default-worker-machinetemplate
         machineHealthCheck:
             maxUnhealthy: 100%
-            # We are intentionally not setting the 'unhealthyConditions' here to test that the field is optional.
+            unhealthyConditions:
+              - type: e2e.remediation.condition
+                status: "False"
+                timeout: 20s
     machinePools:
     - class: k3s-default-worker
       template: