Policies · Legacy policies

TrafficPermission

Legacy allow rules between services under mTLS.

Kuma

Behaviour per target

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

Output: MeshTrafficPermission

Inbound shape: destinations → spec.targetRef, sources → from[] with default.action: Allow. A specific source becomes from[].targetRef: {kind: MeshSubset, tags: <the source's tags>}, the form 2.7+ documents in place of the deprecated kind: MeshService; a kuma.io/service: '*' source becomes kind: Mesh. The destination becomes kind: Dataplane with labels: {app: <name>, k8s.kuma.io/namespace: <ns>} (app is a best guess, warned). Every from[] is reported as deprecated in favour of the rules[] API (removed in 3.0).

--to-latest v3 (3.0) error

No output kind.

Not converted. 3.0 removes MeshTrafficPermission spec.from, and its replacement rules[].default.{allow,deny,allowWithShadowDeny}[] matches clients by SPIFFE ID. That needs a MeshIdentity and its trust domain, which the manifest does not carry, and rules[] is default-deny. The original is copied to _manual/; write an allow entry for every client it let in. Re-run with --to-latest v2 to get the from[] form.

Timeline

VersionChange
2.6New meshes no longer get default TrafficPermission/TrafficRoute resources.
3.0No longer affects generated Envoy configuration; inbounds that relied only on it default to deny.
3.0Removed from the resource registry.

Source files