Policies · Mesh* policies

MeshIdentity

Workload identity (SPIFFE ID and certificate provider) for selected proxies.

Kuma

Behaviour per target

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

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.

--to-latest v3 (3.0) passthrough

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

VersionChange
2.12MeshIdentity and MeshTrust introduced as the successor to Mesh.spec.mtls.
3.0spec.spiffeID is immutable and its trust domain no longer follows the zone. MeshExternalService clusters require a MeshIdentity.

Source files