NoteThis documentation is specific to Linkerd 2.x. For the 1.x branch of development, go here.
Linkerd is a service mesh for Kubernetes and other frameworks. It makes running services easier and safer by giving you runtime debugging, observability, reliability, and security—all without requiring any changes to your code.
For a brief introduction to the service mesh model, we recommend reading What’s a service mesh? And why do I need one?
Linkerd has three basic components: a UI, a data plane, and a control plane. You run Linkerd by:
Once a service is running with Linkerd, you can use Linkerd’s UI to inspect and manipulate it.
You can get started in minutes!
Linkerd works by installing a set of ultralight, transparent proxies next to each service instance. These proxies automatically handle all traffic to and from the service. Because they’re transparent, these proxies act as highly instrumented out-of-process network stacks, sending telemetry to, and receiving control signals from, the control plane. This design allows Linkerd to measure and manipulate traffic to and from your service without introducing excessive latency.
Linkerd is currently published in several tracks: