The Great Sidecar Debate
Talkat KubeCon + CloudNativeCon Europe 2025 · on Wednesday, 2025-04-02· at 15:15· Level 0 | ICC Capital Hall | Room I·
summary
Sidecars remain a concrete engineering tradeoff: Kubernetes now has native sidecar support (merged 2023) and init containers with restartPolicy=Always eliminate many startup/termination warts, but per-pod proxies still cost memory and require pod restarts to update. Alternatives include node proxies and ambient models that split L4 per-node and L7 waypoints (L4 per-node / L7 waypoints), which introduce noisy neighbor risks, larger blast radii and harder resource sizing. Linkerd’s benchmarks show sidecar proxies are smaller and often faster than ambient, so sidecars stay preferred for that stack.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:26What is a sidecar
- 7:04Historical downsides
- 10:15Sidecars in Kubernetes
- 16:24Sidecars versus proxies
- 20:39Multi-tenancy challenges
- 24:12Shared proxy problems
- 26:18Benchmarking sidecars
- 27:43Linkerd prefers sidecars
related talks
05mService Mesh Architectures Explained - Sidecar and Beyond
11mIstio Ambient Mesh: Sidecar vs Sidecar-less, Explained Simply
33mMagic of Kubernetes Sidecar Injection: Present and Future - Anton Ovchinnikov
25mRelease the Kraken: Bring Sidecar Containers to Next Level
31mThe Future of Service Meshes: Sidecarless or eBPF?
25mSidecars at Netflix: From Basic Injection to First Class Ci...
27mPragmatic Pod Patterns: Leveraging sidecar containers in Kubernetes
26mNetworking the Service Mesh Proxy: Where We Are, Where We’re Going
