Policies · Mesh* policies
MeshTrafficPermission
Allows or denies inbound traffic to selected proxies, by client selector (from[]) or SPIFFE identity (rules[]).
Behaviour per target
Output: MeshTrafficPermission
Passed through, with these checks:
spiffeIdis renamed tospiffeID(auto-fixed).action: ALLOW/DENYis reported; useAllow/Deny.from[].targetRef.kind: MeshServiceis reported as deprecated since 2.7.from[]is reported as deprecated in favour ofrules[]and is not converted:rules[]matches clients by SPIFFE ID, needs aMeshIdentityand is default-deny, so a mechanical rewrite would fail or widen access.- A top-level
MeshSubset,MeshServiceorMeshServiceSubsetis reported; useDataplanewith labels.
A policy whose refs still use MeshSubset with kuma.io/service tags, or old
<name>_<ns>_svc_<port> names, is rewritten first (Subset scenario): the top level
becomes Dataplane with labels. from[] keeps MeshSubset with the kuma.io/service
tag (the 2.7+ form); a from[] MeshService with an old _svc_ name is turned back
into that MeshSubset.
Output: MeshTrafficPermission
The v2 checks apply. A policy that keeps from[] is rejected by 3.0 as it stands
(spec.from: unknown field, then "policy must define rules"), so it is written to
_manual/ instead of the apply tree and listed under Action Items → Errors with the
reason. Translate from[] to rules[], then apply it.
Also under v3:
- Empty match entries (
{}) inrules[].default.{allow,deny,allowWithShadowDeny}are reported; 3.0 rejects them. - A top-level
MeshServiceref is rewritten fromname/namespaceto labels, but the kind stays and 3.0 accepts onlyMeshandDataplanethere, so the policy is reported as an error and written to_manual/. - Control-plane-owned labels are removed.
Timeline
| Version | Change |
|---|---|
| 2.7 | from[].targetRef.kind: MeshService deprecated; use MeshSubset with the kuma.io/service tag. |
| 2.14 | from[] deprecated in favour of the SPIFFE-based rules[] API. |
| 3.0 | spec.from removed. Empty match entries rejected. Top-level targetRef limited to Mesh and Dataplane. |
Related topics
- 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.
- 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.