Policies · Legacy policies
HealthCheck
Legacy active health checking of destination endpoints.
Behaviour per target
Output: MeshHealthCheck
Outbound shape. interval, timeout, unhealthyThreshold, healthyThreshold,
tcp.*, http.path and http.expectedStatuses keep their paths.
http.requestHeadersToAdd is split into {add, set} (append unset means add). Header
names are lower-cased, with a warning: the MeshHealthCheck schema accepts lower-case
names only (Accept is rejected) and HTTP header names are case-insensitive.
healthyPanicThreshold is copied to to[].default.healthyPanicThreshold and the scanner
warns that it is deprecated since 2.10 and removed in 3.0: move it to a
MeshCircuitBreaker outlierDetection.healthyPanicThreshold.
Output: MeshHealthCheck, MeshCircuitBreaker
healthyPanicThreshold is removed from the MeshHealthCheck and moved to a companion
MeshCircuitBreaker named <name>-panic-threshold, written as its own file. 3.0 reads
the threshold only when outlier detection is enabled, so the companion also sets
detectors.totalFailures.consecutive: 5. That enables outlier ejection for those
destinations; if a MeshCircuitBreaker already covers them, move the threshold into it
and drop the companion.
References are labels-only. A destination with no kuma.io/service tag is an error.
Timeline
| Version | Change |
|---|---|
| 2.10 | healthyPanicThreshold on MeshHealthCheck deprecated in favour of MeshCircuitBreaker. |
| 3.0 | Removed from the resource registry. |
Related topics
- Legacy policies — The twelve source/destination policies Kuma 3.0 removes, how kuma-migrator maps their selectors and conf to the Mesh* successors, and the two it leaves to you.
- Policy targeting — Which targetRef kinds each policy accepts at each position on 2.14 and 3.0, labels-only selection, policy roles, and control-plane-owned labels.