Migrating a Monolith to Kubernetes
summary
GitHub migrates its decade-old Rails monolith onto Kubernetes, building dynamic staging called review labs that let engineers deploy a change and view it in about a minute; experiments ramp from staff opt-in to 100% traffic served from containers, with about 50 review deployments per workday and roughly 20% services already on Kubernetes. The team ships canary deployments, maintenance modes and a staff toolbar, sees faster onboarding and API-driven control, and notes operational pains (Docker/node instability and a developer learning curve) but deems the migration successful.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 4:45Legacy infrastructure issues
- 12:50Decision to adopt Kubernetes
- 16:31The prototype phase
- 20:35Migration strategy
- 24:03Communication and buy-in
- 28:02Execution and results
- 33:24Lessons and benefits
- 37:41Challenges and looking ahead
related talks
32mOperating Rails in Kubernetes
28mMoving a Monolith from AWS EC2 to K8
40mContainerizing Your Monolith
20mKeynote: The Challenges of Migrating 150+ Microservices to Kubernetes
20mApplication Modernization: From Concept to Kubernetes
18mRe-Architecting Monoliths Into Kubernetes Microservices at Million-User Scale: Hard...
45mHow Kubernetes Was the Secret Sauce in Our Globally Distributed Team’s Transition to Microservices
46mAround & After Kubernetes: The Principles and Ideas that Guide Us