Keynote: Push It to the Limit: From Canary Deployments to Canary Clusters
summary
Lunar moves from canary deployments to full canary clusters by shifting most state out of Kubernetes and automating failover steps: GitOps with Flux, Route 53 via external-dns, RabbitMQ federation, and a small CLI called Shuttle. Two custom operators — cluster identity controller and routing weight controller — inject cluster-specific config and manage DNS weights. After 17 test failovers the end-to-end procedure shrinks from about four hours to 40 minutes with five manual checks.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:50About Henrik
- 3:48Tech stack
- 5:01Shuttle
- 5:51Failover
- 7:49Challenges
- 9:13New controllers
- 9:49Routing weight controller
- 11:21Creating a new cluster
- 12:58New operators
- 13:36Results
- 14:34Goals
related talks
01h 04mThe Fine Art of Canary Deployments
20mKeynote
19mKeynote: Kubernetes Federation
24mKubernetes Multi-cluster and Canary Deployment at the Scale of Qunar
15mKeynote: The Terrifying Migration of 420 Services to Kubernetes
16mKeynote: What a RUSH! Let’s Deploy Straight to Production!
06mKeynote: Beyond Automation: Kubernetes Success Requires a GitOps Mindset
38mScaling Kubernetes Deployments Across +15'000 Namespaces
