How We Built Contour, and What You Can Learn From Our Experience - Dave Cheney, Heptio
summary
Contour is a Kubernetes Ingress controller built on Envoy that translates Kubernetes objects into Envoy via Envoy XDS gRPC; it targets the 80–90% common ingress use cases and ships as ~10,000 lines of code with ~7,000 lines of tests. Design specifics: a work‑group for goroutine lifecycle, a buffered single‑threaded event processing model to avoid races while matching ingresses with secrets, multi‑stage Docker builds with a .dockerignore, dep for dependency management and no checked‑in vendor to keep the repo small.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:41The Philosophy of Ingress
- 8:32Contour Architecture Diagram
- 8:52Kubernetes and Envoy interoperability
- 31:55What are Contour's e2e tests not testing
- 34:03Low lights
- 34:40High Lights
related talks
06mLivin' on the Edge (of your cluster)
20mBuilding an Edge Control Plane with Kubernetes and Envoy
25mKubernetes Ingress: Do More with Less
33mTake Envoy Beyond a K8s Service Mesh - to Legacy Bare Metal & VMs + More
28mDeploying hybrid topologies with k8s & Envoy: a look at service discovery
33mGet to know Envoy - the modern proxy for cloud-native infrastructure - Baptiste Collard
33mIntro: Envoy
33mIntro: Envoy