Policies · Mesh* policies

MeshTrust

CA bundles trusted for a trust domain, used with MeshIdentity.

Kuma

Behaviour per target

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

Output: MeshTrust

spec.origin is reported: removed in 2.13 from the API and the CRD schema, so a strict apply can reject it. The value is published read-only at status.origin.kri. Remove spec.origin.

--to-latest v3 (3.0) warned

Output: MeshTrust

Same check. Control-plane-owned labels are removed.

In a mesh that spans zones, each zone's MeshTrust is synced to the Global only. Create one per zone on the Global, or give every zone the same CA and trust domain. See Trust across zones.

Timeline

VersionChange
2.13spec.origin removed; value moved to status.origin.
3.0The legacy mesh CA is no longer added to the MeshTrust bundle.

Source files