OBSERVABILITY · RELIABILITY · KUBERNETES

Observability and Reliability for Kubernetes

Increase reliability and observability without touching a single line of code in your Kubernetes applications. Linkerd delivers instant insight with golden metrics and Open Telemetry tracing, while enhancing reliablity with automated certificate rotation.

  • 0 lines of instrumentation code required
  • up to 85% reduction in control-plane memory at scale (2.20)
  • every 24 hours automatic proxy cert rotation cycle

Why uniform metrics are hard in a polyglot cluster

Every service emits metrics differently, or not at all, and instrumenting each one by hand across languages and frameworks is extremely challenging. With a service mesh, the operational work is the kind of toil that causes a cluster wide outage when a step is missed.

Linkerd solves this polyglot problem by moving the responsibility of observability out of the application layer and into the platform layer. Instead of changing your code, Linkerd injects a tiny, ultra-fast sidecar proxy (written in Rust) next to every single container in your cluster.

WITHOUT A SERVICE MESH

A project that never finishes

Success Rates: Every service emits status codes differently. No consistent signal across the fleet.

Latency Distributions: p99 slowdowns stay invisible until a end user reports. Teams can measures latency differently.

Request volume (RPS): Throughput lives in dashboards. Scaling runs on intuition.

WITH LINKERD

Done the day you mesh it

Success Rates: Calculated by monitoring HTTP status codes or gRPC response status codes.

Latency Distributions: Tracks how long requests take, breaking them down into percentiles to surface edge-case slowdowns.

Request Volume (RPS): Measures the throughput or number of requests per second hitting a service.

Learn how Linkerd golden metrics are defined for your entire application. Read the blog ↗

What you get

From the moment the proxy is injected, you get consistent golden metrics across every meshed service — no instrumentation, no code changes. The operational work, like certificate rotation, that quietly causes outages gets automated too.

Golden metrics, no instrumentation

Success rate, RPS, and latency percentiles for every meshed service, the moment the proxy is injected.

Cert rotation as a non-event

Linkerd auto-rotates proxy certs every 24 hours. With Buoyant Enterprise for Linkerd (BEL), users can automate even trust anchor rotation.

How does Linkerd observability work?

Linkerd’s proxy reads every meshed connection and records golden metrics (success rate, requests per second, latency percentiles) for HTTP, HTTP/2, and gRPC, with no code change. Those metrics are scraped into Prometheus and surfaced on the dashboard, ready for SLOs and alerts. The control plane issues and rotates identities, and the BEL trust-anchor rotation operator handles the one cert step most likely to cause an outage.

Observability and reliability for kubernetes with Linkerd
Podmeshed traffic(mTLS)PodOpenTelemetryCollectorPrometheusDashboard /Grafana alertsgolden metrics (noapplication changes)clusterPodmeshed traffic(mTLS)PodOpenTelemetryCollectorPrometheusDashboard /Grafana alertsOpenTelemetry traces(mTLS)cluster
1
Every meshed workload automatically and transparently sends golden metrics to Prometheus with no code changes, for use by the Linkerd Dashboard, Grafana, alerting systems, etc.
2
The Linkerd proxy can also be configured to provide more detail for workloads that support OpenTelemetry distributed tracing.

What it covers, and what it doesn’t

Linkerd always provides the golden metrics, and as of2.20, Linkerd exports distributed tracing spans to OpenTelemetry. You’ll still need to pair the mesh with your tracing and APM stack.

L7 TRAFFIC METRICS

Without Buoyant Enterprise for Linkerd

Not included: Full APM or application profiling

Not included: Long-term metrics storage

Not included: Grafana (not bundled since 2.12)

Not included: Trust-anchor rotation automation on OSS / pre-2.20

INCLUDED IN OSS

Included: Success rate, RPS, and latency percentiles, every service

Included: Proxy cert auto-rotation (24 h)

Included: Support for cert-manager issuer rotation

Included: Community support

Buoyant Enterprise for Linkerd

With Buoyant Enterprise for Linkerd

Included: Success rate, RPS, and latency percentiles, every service

Included: Per-service and per-route visibility

Included: Distributed tracing → OpenTelemetry (2.20)

Included: Proxy cert auto-rotation every 24 h

BEL ALSO INCLUDES

Included: Lifecycle automation

Included: Trust anchor rotation automation (2.20)

Included: Continuous security vulnerability scanning

Included: Dedicated enterprise support

Why Linkerd for observability and reliability

  1. Zero-Code Observability

    Automatically capture and visualize crucial L7 golden metrics (latency, success rates, and volume) across all services. As of 2.20, inbound metrics reach parity with outbound, with new HTTP and gRPC duration and frame-size histograms, and distributed tracing spans export to OpenTelemetry following its semantic conventions.

    Read the docs ↗
  2. Automated Zero-Downtime Certificate Rotation

    Introduced in the 2.20 release, it eliminates a major source of operational risk and potential mesh-wide downtime by completely automating mTLS trust anchor renewals and data plane orchestration behind the scenes.

    Read the docs ↗
  3. A lighter control plane at scale

    Linkerd 2.20 refactored the destination controller, which has historically driven most of Linkerd’s memory use, cutting control-plane memory by up to 85% in some cases on large, high-churn clusters.

    Read the docs ↗
  4. Automated GitOps-Ready Upgrades

    The built-in operator entirely automates the toil of control plane updates and data plane proxy rollouts across all clusters, delivering seamless, zero-downtime upgrades that are fully compatible with GitOps tools like Argo and Flux.

    Read the docs ↗
  5. Intelligent, Multi-Zone Reliability

    Ensures high availability and shields your system from single-zone failures using automated retries, circuit breaking, and advanced High Availability Zonal Load Balancing (HAZL).

  6. Enterprise-Scale Resilience

    By layering automated multi-cluster failover and continuous operational diagnostics onto Linkerd’s ultra-fast, memory-safe Rust proxy, BEL guarantees your architecture remains resilient, secure, and cost-effective under heavy production load.

Show me the evidence

Every claim is backed by a reproducible demo, a published cost model, and a CNCF track record.

CASE STUDIES

Outages caught before impact

loveholidayscaught hundreds of failed deployments before they became outages, using SLIs and SLOs built on Linkerd’s metrics.

CASE STUDIES

Trusted in production

Trusted in production by Tradeshift, Expel and teams at Walmart, HP, and Expedia.

COMMUNITY BACKED

CNCF-graduated

Buoyant created Linkerd, coined the term “service mesh,” and shipped the service mesh in July 28, 2021.

Frequently asked questions

Do I need to instrument my code to get metrics?

No. Linkerd records golden metrics at the proxy for all meshed traffic, with no code change.

Does Linkerd replace my APM or tracing?

No. These are L7 traffic metrics; pair them with your tracing and APM tools.

How long are metrics retained?

The bundled Prometheus expires metrics after about 6 hours; export to your own store.

What does cert rotation automate?

Proxy certs rotate every 24 hours on their own; cert-manager automates issuer rotation; the BEL 2.20 operator automates trust-anchor rotation.