Oops, I deployed too hard
summary
A single bash script automates deploys and accidentally overwrites 419 with 420 during a Friday lunch, unlocking a laptop and triggering a customer outage, lawyer threats and hours in a war room; fixes include adding a yes confirmation prompt, restricting Friday deploys, and integrating Jenkins, Artifactory, Puppet, Kong, Grafana/Prometheus and Git, then a yearlong migration that migrated to Kubernetes in one year and adopted Argo CD and Flux for safer GitOps.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 5:37Early DevOps struggles
- 9:53Security and tribal knowledge issues
- 12:17The biggest mistake
- 16:57Consequences and lessons learned
- 19:46Platform evolution and improvements
- 21:37Key takeaways and closing
related talks
43mContinuous Deployment: The GitOps, The Pipelines, and The Ugly
34mGitOps for the people
24m"Misadventures in Continuous Delivery"
55mDevOps @Scale (Greek Tragedy in 3 Acts)
43mHow GitOps Enabled Us to Answer an Unanswerable Question
52mDevops @Scale
54mFrom Code to Customer
35mPanel: GitOps User Stories