Linkerd End User Panel: Case Studies from Production
summary
Linkerd is used in production to solve concrete problems: gRPC load balancing replaces brittle client-side routing for ~40 microservices, mutual TLS encrypts all pod-to-pod traffic for compliance, and multi-cluster mirroring centralizes logs and metrics to a single observability stack. Teams report 80–85% cost reduction on one migration, found socket-reuse bugs before Black Week, use traffic-splitting canaries for rollouts, and automate certificate rotation into an auto-rotating certificates workflow after initial rollout pain; proxies require careful restart and tuning at scale.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:00GRPC Load Balancing
- 4:00Reliability Visibility Security
- 5:25Linkerd Adoption
- 11:05Service Provider
- 11:55Centralized Services
- 13:40MultiCluster
- 16:05Business Impact
- 20:00Advice
- 23:55Biggest challenges
- 25:30Day 2 experience
- 27:25Future of service mesh
- 31:15Automated failover
related talks
35mDeep Dive: Linkerd
01h 03mLinkerd Salon
32mLinkerd and the Service Mesh
12mService Mesh & Kubernetes Multicluster Communication With Linkerd
30mLinkerd Update: Gateway API, Client-Specific Policy, Federated Services, Multicluster, Rust, & More!
35mIntro: Linkerd
05m⚡ Lightning Talk: Increasing Platform Reliability and Performance in One Week with a Service Mesh
28mZero-Cost Linkerd at Adidas: Impossible Is Nothing