Feb 21, 2024: Announcing Linkerd 2.15 with support for VM workloads, native sidecars, and SPIFFE! Read more »

This is not the latest version of Linkerd!
This documentation is for an older version of Linkerd. In Linkerd 2.15 (current), this document no longer exists.

Dynamic Request Routing

Linkerd’s dynamic request routing allows you to control routing of HTTP and gRPC traffic based on properties of the request, including verb, method, query parameters, and headers. For example, you can route all requests that match a specific URL pattern to a given backend; or you can route traffic with a particular header to a different service.

This is an example of client-side policy, i.e. ways to dynamically configure Linkerd’s behavior when it is sending requests from a meshed pod.

Dynamic request routing is built on Kubernetes’s Gateway API types, especially HTTPRoute.

This feature extends Linkerd’s traffic routing capabilities beyond those of traffic splits, which only provide percentage-based splits.

Learning more