Policies · Mesh* policies
MeshPassthrough
Controls which destinations outside the mesh transparent-proxy traffic may reach.
Behaviour per target
Output: MeshPassthrough
Copied unchanged. appendMatch[] entries 2.14 rejects are reported: partial wildcards
(*foo.com), type: Domain with tcp/mysql, and a wildcard domain on an L7 protocol
without a port. Matches that resolve to the same Envoy filter chain are reported too.
Output: MeshPassthrough
v2 checks, plus a non-wildcard type: Domain match without a port is reported (3.0
resolves the domain itself and needs the port).
A Mesh with networking.outbound.passthrough: true gets a companion
MeshPassthrough with passthroughMode: All (see Mesh): 3.0 drops
external traffic for any transparent-proxy data plane no MeshPassthrough selects.
Timeline
| Version | Change |
|---|---|
| 2.10 | Kubernetes and Universal default passthroughMode unified. |
| 2.14 | Partial wildcards and invalid domain/protocol combinations rejected. |
| 3.0 | Domain matches need a port; colliding filter chains rejected; outbound passthrough defaults to None. |
Related topics
- External services — ExternalService to MeshExternalService, the SecureDataSource TLS shape, MeshPassthrough, and what Kuma 3.0 requires for traffic leaving the mesh.