Policies · Mesh* policies

MeshHealthCheck

Active health checks against outbound destinations.

Kuma

Behaviour per target

--to-latest v2 (2.x) warned

Output: MeshHealthCheck

Copied unchanged. healthyPanicThreshold is reported: deprecated since 2.10, removed in 3.0. Set it on a MeshCircuitBreaker with the same targetRef and to[].targetRef, as to[].default.outlierDetection.healthyPanicThreshold.

--to-latest v3 (3.0) rewritten

Output: MeshHealthCheck, MeshCircuitBreaker

to[].default.healthyPanicThreshold is removed and moved to a companion MeshCircuitBreaker named <name>-panic-threshold, written as its own file in the input's format (Universal or Kubernetes) and namespace (the system namespace when the MeshHealthCheck has none). It keeps the same spec.targetRef and to[].targetRef, rewritten to labels like the MeshHealthCheck's. Both 2.14 and 3.0 reject outlierDetection without a detector, so the companion sets detectors.totalFailures.consecutive: 5; that turns on outlier ejection for those destinations, and the warning says so. If a MeshCircuitBreaker already covers them, move the threshold into it and drop the companion. The same applies to a MeshHealthCheck converted from a legacy HealthCheck.

Labels-only refs and control-plane label removal also apply. Allowed to[].targetRef.kind: Mesh, MeshService, MeshExternalService, MeshMultiZoneService.

Timeline

VersionChange
2.10healthyPanicThreshold deprecated in favour of MeshCircuitBreaker.
3.0healthyPanicThreshold removed and dropped silently; Envoy falls back to its 50% default.

Source files