Policies · Legacy policies
FaultInjection
Legacy HTTP delays, aborts and bandwidth limits injected on a destination's inbound.
Behaviour per target
Output: MeshFaultInjection
Inbound shape: destinations → spec.targetRef (Dataplane labels), sources →
from[] as kind: MeshSubset with the source's tags (kind: Mesh for
kuma.io/service: '*'), not the 2.7-deprecated MeshService. Reserved tags such as
kuma.io/protocol are dropped from the Dataplane labels, with a warning. The single
legacy conf becomes a one-element default.http[] list (delay, abort,
responseBandwidth). Percentages are numbers when whole and strings when fractional.
responseBandwidth.limit is rewritten with the units MeshFaultInjection accepts
(50 mbps → 50Mbps, kbps, Gbps), with a warning; a value that is not
<integer><unit> is copied and warned, because the control plane rejects it.
The scanner then warns that from[] is deprecated in favour of rules[].
Output: MeshFaultInjection
Converted to rules[] (no matches[]) only when every source is
kuma.io/service: '*', which keeps the "all clients" scope. Any specific source is an
error: rules[].matches[] selects clients by SPIFFE ID or SNI, which the manifest
does not carry. The original goes to _manual/.
Timeline
| Version | Change |
|---|---|
| 2.10 | No longer generates Envoy configuration. |
| 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.