The Cilium Story - Why We Created Cilium
summary
Project starts in 2015 to replace traditional CNI behavior by building an eBPF dataplane that ships L3/L4 networking, network policy, transparent encryption and a kube-proxy replacement; early IPv6‑only prototype adds IPv4 later. Observable features come as Hubble observability with UI and CLI, multi‑cluster via cluster mesh, load balancing, and runtime security via Tetragon enforcement. Vendors adopt it, eBPF reaches Windows, and a Transit Gateway extends Cilium Mesh to VMs and existing networks. Kernel support targets ~4.9–4.19.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:49First Cilium Commit
- 4:461st Cilium Design Summit
- 5:07First Conference Talks
- 6:56The Beginning
- 7:37Network Policy
- 9:28Cluster Mesh
- 14:06Cilium Service Mesh
- 16:10Roadmap Highlights
related talks
07mThe Cilium Vision
44mCilium - Container Security and Networking Using BPF and XDP
05mLightning Talk: Unveiling 5 Essential Insights from Cilium Implementation in a...
20mTackling Container Networking at Scale
35mNext-level Kubernetes Networking with Cilium - Nico Meisenzahl and Philip Welz
27mCilium Cluster Mesh: The eBPF-Powered Multicluster Solution for Kubernetes
31mCilium Mesh
29mThe Swiss Army Knife of Cloud Native Networking
