Migrating GitLab.com to Kubernetes: How Multiple Clusters Saved Cost
Talkat KubeCon + CloudNativeCon North America 2021 · on Friday, 2021-10-15· at 11:55· Concourse Hall 152 + Online·
summary
Migrating stateless services (Container Registry, background workers, Git requests) from VMs to GKE exposes a regional-cluster problem where roughly two thirds of traffic can cross zones, turning 500 TB → $5k/month into recurring egress spend; the fix is per-zone clusters so ingress controllers route only to local pods, which removes most cross-zone egress, reduces network bills, enables staged upgrades, cluster-level A/B testing, and avoids NAT port exhaustion during simultaneous image pulls.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:27Agenda
- 0:51GitLabcom Overview
- 2:15Getting Started with Kubernetes
- 3:41GitLab Container
- 5:34Cloud Costs
- 9:30Web Service Pods
- 10:30Multiple Clusters
- 12:21Service Mesh
- 13:31Complexity
- 14:44Mitigation
- 15:50Testing
- 16:55Maintenance Procedures
- 17:42Wrap Up
related talks
26mRunning GitLab and GitLab CI in Kubernetes for the Enterprise
05mMoving to Kubernetes, or not?
14mCut Costs, Not Performance: Implement Kubernetes Cost Optimization Strategies
33mSpace Invaders for Kubernetes: Consolidating 50 Clusters at Scale
15mDemo: Resource(Cost) optimization on planet scale Kubernetes clusters.
38mBuilding the Perfect Infrastructure with Kubernetes
29mBest Practices for Kubernetes Runners
29mScaling Across the Enterprise