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.

HTTP, HTTP/2, and gRPC Proxying

Linkerd can proxy all TCP connections. For HTTP connections (including HTTP/1.0, HTTP/1.1, HTTP/2, and gRPC connections), it will automatically enable advanced L7 features including request-level metrics, latency-aware load balancing, retries, and more.

(See TCP Proxying and Protocol Detection for details of how this detection happens automatically, and how it can sometimes fail.)

Note that while Linkerd does zero-config mutual TLS, it cannot decrypt TLS connections initiated by the outside world. For example, if you have a TLS connection from outside the cluster, or if your application does HTTP/2 plus TLS, Linkerd will treat these connections as raw TCP streams. To take advantage of Linkerd’s full array of L7 features, communication between meshed pods must be TLS’d by Linkerd, not by the application itself.