Policies · Legacy policies
CircuitBreaker
Legacy outlier detection and connection limits for a destination service.
Behaviour per target
Output: MeshCircuitBreaker
Outbound shape (sources → spec.targetRef, destinations → to[]). The flat legacy
conf is split in two:
Legacy conf |
MeshCircuitBreaker to[].default |
|---|---|
thresholds.{maxConnections,maxPendingRequests,maxRequests,maxRetries} |
connectionLimits.* |
interval, baseEjectionTime, maxEjectionPercent, splitExternalAndLocalErrors |
outlierDetection.* |
detectors.totalErrors |
outlierDetection.detectors.totalFailures |
detectors.gatewayErrors |
outlierDetection.detectors.gatewayFailures |
detectors.localErrors |
outlierDetection.detectors.localOriginFailures |
detectors.standardDeviation.{requestVolume,minimumHosts,factor} |
outlierDetection.detectors.successRate.{requestVolume,minimumHosts,standardDeviationFactor} |
detectors.failure.* |
outlierDetection.detectors.failurePercentage.* |
Unmapped leaves are reported. Targeting rules are the same as for Timeout.
Output: MeshCircuitBreaker
Same conversion, with labels-only references (see Timeout). A
destination with no kuma.io/service tag is an error and the original goes to _manual/.
The source object is listed under "Delete Before Upgrading to 3.0".
Timeline
| Version | Change |
|---|---|
| 3.0 | Removed from the resource registry. Stored objects are not migrated. |
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.