Intro: Linkerd
summary
Linkerd presents a CNCF service mesh with a Rust data plane proxy and Go control plane that is already in production for over 24 months. It ships mTLS on by default, exposes aggregated metrics via Prometheus (temporary retention ~6 hours), and 2.3 adds telemetry, retries, timeouts and auto‑inject while 2.4 targets traffic shifting. Non‑HTTP traffic is proxied as TCP streams, installation is sidecar injection per service for incremental rollout, and development cadence is weekly edge and ~six‑week stable releases. service profiles opt‑in
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:38What is Linkerd
- 3:58Why use Linkerd
- 7:03Linkerd history
- 8:53Design goals
- 12:03Data plane
- 14:01Roadmap
- 15:51CoopCon EU
- 20:10QA
- 21:15Twitter
- 22:19Co vs Linkerd
- 23:43Focus on Operational Simplicity
- 28:31Prometheus
- 31:44Linkerd
related talks
35mNavigating the Service Mesh Ecosystem
04mInterview
30mService Mesh Is Still Hard. The Things we all Did Wrong & Tales of Woe
34mService Mess to Service Mesh
27mService Mess to Service Mesh
33mService Meshes: Istio, Linkerd - or No Mesh at All?
35mUpgrading Your Service Mesh to Linkerd 2
28mHow a Service Mesh Helped Us Build Production Cloud-Native Services
