Merge pull request #35060 from bobfuru/BZ1858166

BZ1858166 Clarify maxUnhealthy in machine health check

Author: Bob Furu

modules/machine-health-checks-resource.adoc

@@ -60,6 +60,8 @@ Remediation is not performed if the number of unhealthy machines exceeds the `ma
 If `maxUnhealthy` is not set, the value defaults to `100%` and the machines are remediated regardless of the state of the cluster.
 ====
 
+The appropriate `maxUnhealthy` value depends on the scale of the cluster you deploy and how many machines the `MachineHealthCheck` covers. For example, you can use the `maxUnhealthy` value to cover multiple machine sets across multiple availability zones so that if you lose an entire zone, your `maxUnhealthy` setting prevents further remediation within the cluster.
+
 The `maxUnhealthy` field can be set as either an integer or percentage.
 There are different remediation implementations depending on the `maxUnhealthy` value.