Stop Reading Changelogs: Safer Kubernetes Upgrades with Simulation
summary
An open-source tool called SimKube records production activity as a timestamped YAML trace and replays it into a simulated cluster built on KWOK (Kubernetes without kubelet) so thousands of nodes and pods run on a laptop. It catches concrete upgrade breakages — example: cronjob API removal (batch/v1beta1 → batch/v1) — and lets users apply a SKEL transform to rewrite traces, rerun simulation, and validate fixes; limitations include no real application code, missing metric-driven controllers, and opaque managed control planes.
AI-written summary · about
chapters (16)
- 0:00Safer Kubernetes upgrades
- 1:42Introduction
- 3:26SimCube and why it matters
- 5:12Kubernetes upgrade challenges
- 9:09Test clusters aren't enough
- 11:17Simulation is the missing tool
- 13:27SimCube captures cluster state
- 15:35SimCube architecture
- 17:01Trace files in practice
- 19:54Simulate workloads locally
- 20:56Upgrading in simulation
- 24:09Fixing issues with SKEL
- 27:01Automating upgrades with CI
- 29:09Simulation benefits and limits
- 32:37Simulation vs Reddit’s outage
- 33:58Resources and closing
related talks
36mA Toolkit for Simulating Kubernetes Scheduling at Scale
27mUnderstanding Kube-Scheduler-Simulator
28mHow We Tackle KubeVirt’s Growth and Scalability
17mtalk Kubernetes with
30mTesting Kubernetes Clusters - Building Confidence in Your Changes
45mWhat I Learnt Fixing 50+ Broken Kubernetes Clusters
46mEnd-Users Won't Even Notice, Painless Kubernetes Upgrades
25mAutomating Kubernetes Upgrades for Zero Downtime