Policies · Other resources
MeshExternalService
An external destination reachable from the mesh through zone egress.
Behaviour per target
Output: MeshExternalService
Copied unchanged. spec.tls.verification.{caCert,clientCert,clientKey} in the flat
DataSource shape (inline, inlineString, secret) are reported: 3.0 requires
SecureDataSource, and 2.14.6+ accepts both. Names that are not RFC 1035 labels are
reported.
Output: MeshExternalService
inlineString→type: InsecureInline+insecureInline.value;secret→type: Secret+secretRef. Apply while every control plane runs 2.14.6 or later, before the Global upgrade: the Apply Checklist has a step for it.inline(base64) is not converted: that means decoding credential material into plain text, which is your decision. 3.0 rejects the field (spec.tls.verification.caCert.inline: unknown field), so the MeshExternalService is written to_manual/; rewrite it astype: Secret+secretRef(orInsecureInline) and apply it from there.- A
kuma.io/zonelabel is reported: 3.0 removes per-zone routing and every zone's egress dials the endpoint directly. - A mesh with no
MeshIdentityin the input set is reported: 3.0 builds the cluster only for clients with a workload identity, else503 cluster_not_found.
Timeline
| Version | Change |
|---|---|
| 2.9 | Unix socket endpoints removed. |
| 2.14.6 | TLS verification accepts the SecureDataSource shape. |
| 3.0 | SecureDataSource required; per-zone routing removed; clusters require a MeshIdentity; non-RFC 1035 names rejected. |
Related topics
- External services — ExternalService to MeshExternalService, the SecureDataSource TLS shape, MeshPassthrough, and what Kuma 3.0 requires for traffic leaving the mesh.
- 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.