skip to Main Content

How we designed retries in Linkerd 2.2

  • February 22, 2019

Retries are a fundamental mechanism for handling partial or transient failures in a distributed system. But retries can also be dangerous—if done poorly, they can rapidly escalate a small error…

More

Announcing Linkerd 2.2

  • February 12, 2019

Today we're very happy to announce the release of Linkerd 2.2. This major release introduces automatic request retries and timeouts, and graduates auto-inject to be a fully-supported (non-experimental) feature. It…

More

Service Profiles for Per-Route Metrics

  • December 7, 2018

One of the primary goals of Linkerd is to enable service and platform owners alike to understand their services not just in terms of packets and bytes, but in terms…

More

Announcing Linkerd 2.1

  • December 6, 2018

Today we're very happy to announce the release of Linkerd 2.1. This is our first stable update to 2.0, and introduces a host of goodies, including per-route metrics, service profiles,…

More

Announcing Linkerd 2.0

  • September 18, 2018

On behalf of the Linkerd maintainers, I’m happy to announce that Linkerd 2.0 is now in general availability (GA). This means that we’ve cut an official 2.0 stable release, and…

More

Conduit 0.5.0 and the future of Conduit

  • July 6, 2018

Conduit is now part of Linkerd! Read more > Today we're very happy to announce Conduit 0.5.0, which introduces zero-config automatic TLS between mesh'd pods (including certificate creation and distribution).…

More

Conduit 0.4.0: Where’s my traffic?

  • April 20, 2018

Conduit is now part of Linkerd! Read more > Earlier this week, we released Conduit v0.4.0. This release has some significant improvements to the Prometheus-based telemetry system, and introduces some…

More