You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/book/src/tasks/healthcheck.md
+10-1Lines changed: 10 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
Before attempting to configure a MachineHealthCheck, you should have a working [management cluster] with at least one MachineDeployment or MachineSet deployed.
6
6
7
-
<asideclass="note warn">
7
+
<asideclass="note warning">
8
8
9
9
<h1> Important </h1>
10
10
@@ -53,6 +53,15 @@ spec:
53
53
timeout: 300s
54
54
```
55
55
56
+
<aside class="note warning">
57
+
58
+
<h1> Important </h1>
59
+
60
+
If you are defining more than one `MachineHealthCheck` for the same Cluster, make sure that the selectors **do not overlap**
61
+
n order to prevent conflicts or unexpected behaviors when trying to remediate the same set of machines.
62
+
63
+
</aside>
64
+
56
65
## Remediation short-circuiting
57
66
58
67
To ensure that MachineHealthChecks only remediate Machines when the cluster is healthy,
0 commit comments