Policies · Mesh* policies

MeshHTTPRoute

HTTP routing (matches, filters, weighted backends) for outbound traffic to a service.

Kuma

Behaviour per target

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

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).

--to-latest v3 (3.0) rewritten

Output: MeshHTTPRoute

  • to[].targetRef and backendRefs[] name/namespace/mesh → labels.
  • Route with no catch-all rule (empty matches[] or PathPrefix: /) is reported: on 3.0 an unmatched request gets a 404 across every HTTP port of the destination.
  • MeshServiceSubset backendRefs are reported.
  • A backendRefs[] entry whose port or sectionName matches no port of the MeshService in the input (by name or port number, never targetPort) is reported: on 3.0 it is unresolved instead of falling through to another port, and a rule whose backendRefs are all unresolved answers 500. A MeshService missing from the input is noted once per run.
  • Allowed to[].targetRef.kind: MeshService, MeshExternalService, MeshMultiZoneService.

The targetRef matrix is in Policy targeting.

Timeline

VersionChange
3.0Unmatched requests get a 404. MeshServiceSubset backendRefs rejected. Real resources selected by labels only. A backendRef naming a port the destination lacks fails closed.

Source files