Revolutionizing Mesh Layers: Transitioning from Istio to Cilium at...
summary
New York Times migrates much of its mesh from Istio to Cilium/eBPF, cutting sidecar proliferation and simplifying cross‑region traffic by removing extra load balancers and Envoy hops; an operator distributes and keeps Cilium network policies in sync across regions, Helm unit tests validate tenant policy templates, and Hubble flow logs handle debugging. Claims include a measurable reduction in resource footprint (about half of containers were sidecars in the old setup), replaces many Istio components, and operator syncs Cilium policies.
AI-written summary · about
chapters (12)
- 0:00Introduction to the New York Times platform
- 1:26Platform foundation & multi-tenancy
- 3:34Strict Kubernetes isolation
- 6:58Istio’s complex mesh issues
- 7:20Cilium & eBPF transition
- 8:50Multi-region failover strategies
- 10:36Automating Cilium policies
- 11:38Simplified tenant authorization
- 12:44Consolidation opportunities
- 13:29Reducing traffic hops
- 15:16Key takeaways
- 17:52Q&A
related talks
11mCilium Service Mesh
35mNext-level Kubernetes Networking with Cilium - Nico Meisenzahl and Philip Welz
31mCilium Mesh
24mThe Cilium Story - Why We Created Cilium
20mTackling Container Networking at Scale
27mCilium Cluster Mesh: The eBPF-Powered Multicluster Solution for Kubernetes
32mBreaking Boundaries: Multi-cluster with Cilium cluster mesh
16mCilium Wars: Scaling Up Your Network with Jedi-like Cilium Handling Techniques - Yash Tandon