Overview And State Of Linkerd
summary
Linkerd is a lightweight service mesh built around a Rust proxy that enforces mTLS by default, bootstraps identities from Kubernetes service accounts, and targets low resource use. Recent releases add server-side authorization (2.11), gRPC retries with a 64k retry buffer, and a Rust policy controller; 2.12 adds per-route auth via the Gateway API HTTPRoute and auto health-check handling. Roadmap includes client-side policy in 2.13: header-based routing, circuit-breaking, and migrating service profiles to Gateway-native configuration.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:05What is Linkerd
- 3:32Linkerd philosophy
- 7:05Linkerd vs Istio
- 8:09Linkerd 2.11 features
- 11:39Rust in control plane
- 13:08Server-side policy 2.12
- 15:56Gateway API integration
- 17:01Linkerd 2.13 features
- 22:20Get involved with Linkerd
- 24:36Q&A: Ambient mesh
- 26:19Q&A: Upgrading Linkerd
- 28:03Q&A: Security layers
- 29:29Q&A: Certificate management
- 30:11Q&A: Visibility and routing
- 31:15Q&A: Control plane
- 31:58Q&A: Back pressure
- 32:40Q&A: User auth & East-West
- 33:44Q&A: OPA & data policies
- 34:05Q&A: Control plane comms
related talks
19mOverview and State of Linkerd
20mOverview and State of Linkerd
27mThe Future of Linkerd: 2.18 and Beyond
39mSeamless multi-cluster Communication and Observability with Linkerd
32mBeyond Security – Using Linkerd to Get Metrics
29mObservability and Debugging Cloud-Native Apps using Linkerd & Conduit
23mPanel: The State Of Service Mesh
29mDebugging an app with a service mesh