Policies · Legacy policies

CircuitBreaker

Legacy outlier detection and connection limits for a destination service.

Kuma

Behaviour per target

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

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.

--to-latest v3 (3.0) converted

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

VersionChange
3.0Removed from the resource registry. Stored objects are not migrated.

Source files