Policies · Mesh* policies
MeshTLS
TLS mode (Strict/Permissive), versions and ciphers for mesh traffic.
Behaviour per target
Output: MeshTLS
from[] → rules[] (see MeshTimeout). The 2.9-era from[]
shape is converted; the client selector is dropped.
Output: MeshTLS
Same rewrite plus control-plane label removal. On 3.0 an unconverted from is dropped
silently, which can flip inbounds between strict and permissive.
A Mesh whose enabled mTLS backend is PERMISSIVE gets a companion MeshTLS
<mesh>-tls-permissive with rules[].default.mode: Permissive (see Mesh).
Timeline
| Version | Change |
|---|---|
| 2.10 | rules[] API added; from[] deprecated. |
| 3.0 | from removed and silently ignored. Only MeshTLS decides whether an inbound accepts plaintext. |
Related topics
- 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.