Policies · Other resources

MeshExternalService

An external destination reachable from the mesh through zone egress.

Kuma

Behaviour per target

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

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.

--to-latest v3 (3.0) rewritten

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 as type: Secret + secretRef (or InsecureInline) and apply it from there.
  • A kuma.io/zone label is reported: 3.0 removes per-zone routing and every zone's egress dials the endpoint directly.
  • A mesh with no MeshIdentity in the input set is reported: 3.0 builds the cluster only for clients with a workload identity, else 503 cluster_not_found.

Timeline

VersionChange
2.9Unix socket endpoints removed.
2.14.6TLS verification accepts the SecureDataSource shape.
3.0SecureDataSource required; per-zone routing removed; clusters require a MeshIdentity; non-RFC 1035 names rejected.

Source files