We Didn’t Start the Fire: Communication Breakdowns and How to Preven...
summary
History of Kubernetes breaking changes shows concrete failures and fixes: v1beta1 API removals in 1.16 leave many clusters stuck on 1.15 outside patch support, docker‑shim deprecation (announced for 1.20/removed 1.22) triggers widespread panic because users conflate Docker with the container runtime, and a miscoordinated post around pod security policy leads to scrambled messaging. The project creates a contributor comms committee, rewrites FAQ/blog posts, and shifts to coordinated outreach — which reduces future outages and confusion.
AI-written summary · about
chapters (5)
related talks
12mIgnite Karaoke! with Many People
41mBeen There, Done That: Tales of Burnout from the Open Source W...
35mWe're Marketers. If we can Learn Distributed Systems + K8s, so can you!
25mThis is why we can't have nice things!
34mThe Return of the Dull Stack Engineer
15mDevX Experience is broken… and you should be pissed
26mDelivering Bad News: Helping your Community Through a Rough Patch
23mChange Management