Set Your Developers Free: Fleet Management at Spotify
Talkat KubeCon + CloudNativeCon Europe 2025 · on Thursday, 2025-04-03· at 14:15· Level 0 | ICC Capital Hall | Room J·
summary
Spotify runs fleet automation that updates dependencies and resources across thousands of repos and over 10,000 components, claiming a Log4J patch rolled through most services in about 6 hours and 80% of components in ~11 hours, reaching ~99% in days. The system builds a Fleet Shift that spawns Kubernetes jobs per repo, runs Docker transforms, opens GitHub PRs watched by a fleet shift bot, applies automerge when CI passes, and relies on a Golden Tech stack; outcome: major speedup, fewer vulnerabilities, and large developer time savings.
AI-written summary · about
chapters (14)
- 0:00Log4j incident wake-up call
- 3:06War room for fleet fix
- 6:15Fleet shifts for automation
- 9:10Spotify's fleet investment
- 11:43Fleet Shift automates updates
- 14:09Fleet readiness for automation
- 15:54Golden tech in fleet management
- 17:00Fleet beyond software
- 18:45Automated deployment pipeline
- 19:27Scaling fleet automation
- 20:49Code transformations and cleanups
- 21:54AI for fleet migrations
- 22:39Impact on migration time
- 24:05Freeing engineers for features
related talks
31mThe Rise of Internal Developer Portals and the Future with AI
42mNavigating Backstage: A Year in Developer Life
12mValue Driven Platform Engineering Using Backstage
27mShifting Spotify Engineering from Spreadsheets to Backstage
47mImproving Developer Experience with Backstage
39mOwn your speed
41mBackstage.io: Spotify's platform developer experience
26mBackstage: Shaping the Future Of Developer Experience