Policies · Legacy policies
ExternalService
Legacy external destination reached through the mesh, identified by a kuma.io/service tag.
Behaviour per target
Output: MeshExternalService
Kubernetes and Universal layouts are both read.
ExternalService |
MeshExternalService |
|---|---|
networking.address (host:port) |
spec.endpoints[] and spec.match.port |
tags["kuma.io/protocol"] |
spec.match.protocol (tcp if absent) |
networking.tls.enabled, allowRenegotiation |
spec.tls.* |
networking.tls.serverName |
spec.tls.verification.serverName |
networking.tls.{caCert,clientCert,clientKey} |
spec.tls.verification.*, same DataSource shape |
The output keeps the input format: a Universal ExternalService becomes a Universal
MeshExternalService (type/name/mesh), a Kubernetes one becomes a CRD in the
system namespace (see Meshes).
spec.match.type is HostnameGenerator. Warnings remind you to check the virtual port,
the generated hostname and verification.mode (defaults to Secured). The copied TLS
DataSources then get the MeshExternalService 3.0
advisory.
Output: MeshExternalService
Same conversion. The output then goes through the MeshExternalService v3 scan:
inlineString and secret DataSources are rewritten to SecureDataSource, inline
stays warn-only, and a warning fires when the input set has no MeshIdentity for the
mesh. The source object is listed under "Delete Before Upgrading to 3.0".
Timeline
| Version | Change |
|---|---|
| 3.0 | Removed (CRD, API and webhook). Applying one after the upgrade fails. |
Related topics
- External services — ExternalService to MeshExternalService, the SecureDataSource TLS shape, MeshPassthrough, and what Kuma 3.0 requires for traffic leaving the mesh.
- Legacy policies — The twelve source/destination policies Kuma 3.0 removes, how kuma-migrator maps their selectors and conf to the Mesh* successors, and the two it leaves to you.