CAPI vs. ClusterStacks: The Better is the Enemy of the Good
summary
Live demo compares vanilla Cluster API (CAPI) with SCS ClusterStacks and shows CAPI alone leaves gaps around CNI/CSI, node images, and safe upgrades while ClusterStacks packages Kubernetes config, node images + CNI/CSI bundled, and cluster classes into atomic, versioned stacks that are integration-tested and deployed atomically. Claim: stacks reduce night-time rollbacks and can update across 500 clusters using rolling updates. Works today on Sovereign Cloud Stack, has a Docker single-node dev path and needs cloud‑in‑a‑box or 32GB+ for realistic testing; bare‑metal support is theoretical.
AI-written summary · about
chapters (15)
- 0:00Introduction and setup
- 1:04Speaker introductions
- 2:27Kubernetes at scale challenges
- 3:53CubeADM and CubeSpray limitations
- 5:19Cluster API overview
- 6:42Introducing Cluster Stacks
- 8:49Cluster Stacks benefits
- 10:37Atomic updates and testing
- 12:04Cluster Stacks limitations
- 13:06Training and resources
- 14:34Call to action
- 15:17Q&A: Single cluster benefits
- 16:42Q&A: Local testing options
- 17:44Q&A: Bare metal support
- 19:50Closing remarks
related talks
08mManaging Thousands of Kubernetes Clusters with Cluster API and No Monitoring Stack
39mCluster API & Cluster Autoscaler
04mIntro
45mLet Them Eat CAKES: A Sweet Dive Into a Modern Cloud Networking Stack
23mBuilding public cloud service on Cozystack
09mFrom AWS EC2 to Cozystack: A Beginner’s Roadmap to Cloud Independence
25mIntroduction To Cluster API
52mCloud Native Developer Experience in 2025