Policies · Mesh* policies
MeshHTTPRoute
HTTP routing (matches, filters, weighted backends) for outbound traffic to a service.
Behaviour per target
Output: MeshHTTPRoute
Not converted: MeshHTTPRoute survives 3.0 and is what Kuma compiles Gateway API
HTTPRoute/GRPCRoute into. A MeshServiceSubset backendRefs[].kind is reported
(rejected on 3.0; split the destination into separate MeshService resources).
Output: MeshHTTPRoute
to[].targetRefandbackendRefs[]name/namespace/mesh→ labels.- Route with no catch-all rule (empty
matches[]orPathPrefix: /) is reported: on 3.0 an unmatched request gets a404across every HTTP port of the destination. MeshServiceSubsetbackendRefs are reported.- A
backendRefs[]entry whoseportorsectionNamematches no port of theMeshServicein the input (by name or port number, nevertargetPort) is reported: on 3.0 it is unresolved instead of falling through to another port, and a rule whose backendRefs are all unresolved answers500. AMeshServicemissing from the input is noted once per run. - Allowed
to[].targetRef.kind:MeshService,MeshExternalService,MeshMultiZoneService.
The targetRef matrix is in Policy targeting.
Timeline
| Version | Change |
|---|---|
| 3.0 | Unmatched requests get a 404. MeshServiceSubset backendRefs rejected. Real resources selected by labels only. A backendRef naming a port the destination lacks fails closed. |
Related topics
- Gateways, Gateway API and GAMMA — The built-in gateway removal in Kuma 3.0, MeshGateway* to Gateway API, delegated gateways, and why MeshHTTPRoute and MeshTCPRoute stay.
- Policy targeting — Which targetRef kinds each policy accepts at each position on 2.14 and 3.0, labels-only selection, policy roles, and control-plane-owned labels.