Features

Authorization Policy. Linkerd can restrict which types of traffic are allowed to .

. Linkerd automatically enables mutual Transport Layer Security (TLS) for all communication between meshed applications.

Automatic Proxy Injection. Linkerd will automatically inject the data plane proxy into your pods based annotations.

. Linkerd can optionally use a CNI plugin instead of an init-container to avoid NET_ADMIN capabilities.

Distributed Tracing. You can enable distributed tracing support in Linkerd.

. The Linkerd control plane can run in high availability (HA) mode.

HTTP, HTTP/2, and gRPC Proxying. Linkerd will automatically enable advanced features (including metrics, load balancing, retries, and more) for HTTP, HTTP/2, and gRPC connections.

. Linkerd can work alongside your ingress controller of choice.

Load Balancing. Linkerd automatically load balances requests across all destination endpoints on HTTP, HTTP/2, and gRPC connections.

. Linkerd can transparently and securely connect services that are running in different clusters.

Retries and Timeouts. Linkerd can perform service-specific retries and timeouts.

. Linkerd’s service profiles enable per-route metrics as well as retries and timeouts.

TCP Proxying and Protocol Detection. Linkerd is capable of proxying all TCP traffic, including TLS’d connections, WebSockets, and HTTP tunneling.

. Linkerd automatically collects metrics from all services that send traffic through it.

Traffic Split (canaries, blue/green deploys). Linkerd can dynamically send a portion of traffic to different services.