Policies · Legacy policies
TrafficPermission
Legacy allow rules between services under mTLS.
Behaviour per target
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).
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
| Version | Change |
|---|---|
| 2.6 | New meshes no longer get default TrafficPermission/TrafficRoute resources. |
| 3.0 | No longer affects generated Envoy configuration; inbounds that relied only on it default to deny. |
| 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.
- Access control — MeshTrafficPermission from[] versus SPIFFE rules[], MeshOPA, and the Kong Mesh RBAC changes in 3.0 — what kuma-migrator converts and what stays manual.
- mTLS and workload identity — Moving a mesh from Mesh.mtls to MeshIdentity and MeshTrust before Kuma 3.0, and why kuma-migrator reports it instead of rewriting it.