
Linkerd 2.14 End of Life
Linkerd 2.14 reached its end of life on June 1, 2025, and we strongly recommend that you upgrade.

Linkerd 2.14 reached its end of life on June 1, 2025, and we strongly recommend that you upgrade.

Over the last year or so, we’ve seen a lot of confusion about “sidecars or sidecarless” in the context of service meshes. This architectural choice turns out to be very important – not because of sidecars per se, but because it deeply affects how the mesh approaches sharing and multi-tenancy.
A great many Linkerd installations use cert-manager and trust-manager to excellent effect, and you can read all about how to set this up in the Linkerd documentation. Recently, though, cert-manager made a change that has the potential to disrupt Linkerd installations with a particularly subtle misconfiguration.

We're happy to announce the release of Linkerd 2.18. The theme of this release is battlescars: we've added features and updated functionality to reduce operational pain in response to real life, hard-won lessons we've learned with our customers who have pushed the limits of what Linkerd (and Kubernetes itself!) can do.

Today, we're happy to announce the release of Linkerd 2.17, a new version of Linkerd that introduces several major new features to the project: egress traffic visibility and control; rate limiting; and federated services, a powerful new multicluster primitive that combines services running in multiple clusters into a single logical service.

Today we're happy to announce Linkerd 2.16, a major step forward for Linkerd that adds a whole host of new features, including support for IPv6; an "audit mode" for Linkerd's zero trust security policies; a new implementation of retries, timeouts, and per-route metrics for HTTPRoute and GPRCRoute resources; and much more.

In this guide we'll walk you through a task that is increasingly common in the Kubernetes space: migrating an existing Istio deployment to Linkerd.

Transitioning core service mesh functionality between Istio and Linkerd is not overly complicated. Chances are you're using Istio for things that Linkerd also supports.

Topology Aware Routing is a feature of Kubernetes that prevents cluster traffic within one availability zone from crossing to another availability zone. For high-traffic applications deployed in multi-zone clusters, this can provide significant cost savings. However, Topology Aware Routing is designed to always prohibit cross-zone traffic, regardless of overall system health or performance.

Today we're happy to announce the release of Buoyant Enterprise for Linkerd 2.15.3. This latest stable release includes several backported bug fixes, especially for native sidecars, as well as introducing usability improvements and new diagnostic and configuration features.

Today, we're happy to announce pod-based pricing for Buoyant Enterprise for Linkerd. This new pricing is designed to give our adopters a clear way and transparent picture of the cost of BEL, to be fair and commensurate with Linkerd's value, and to avoid penalizing specific architectural decisions and technical decisions that are independent of how Linkerd is used.

Today we're happy to announce the release of Buoyant Enterprise for Linkerd 2.15.2. This release makes our high-availability zonal load balancer (HAZL) available in the standard proxy build, and includes several feature improvements and bugfixes, including for a memory leak in the security policy controller.