Policies · Mesh* policies
MeshIdentity
Workload identity (SPIFFE ID and certificate provider) for selected proxies.
Behaviour per target
Output: MeshIdentity
Copied unchanged. The migrator never generates a MeshIdentity: moving off
Mesh.spec.mtls is a CA cutover whose trust domain, SPIFFE paths and key material are
not in the manifests. See Mesh for the advisory.
Every MeshIdentity in the input is indexed by mesh, for the MeshExternalService check
under v3.
Output: MeshIdentity
Copied unchanged apart from control-plane label removal. Its presence suppresses the MeshExternalService "no MeshIdentity" warning for that mesh.
A Bundled provider with autogenerate, or with a ca that is a self-signed root,
needs insecureAllowSelfSigned: true, or it never becomes ready. Each zone generates its
own CA: see Trust across zones.
Timeline
| Version | Change |
|---|---|
| 2.12 | MeshIdentity and MeshTrust introduced as the successor to Mesh.spec.mtls. |
| 3.0 | spec.spiffeID is immutable and its trust domain no longer follows the zone. MeshExternalService clusters require a MeshIdentity. |
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.