Space Invaders for Kubernetes: Consolidating 50 Clusters at Scale
summary
Company consolidates ~50 single-tenant clusters into three shared multi-tenant EKS clusters, cutting standing costs that made >60% of clusters more expensive than their use. Deployment standardizes on Argo CD with Git repos and namespace-based isolation; secrets flow via an external-secret operator. A custom VPC-peering tool plus an AI wizard automates cross-account networking. Cost is allocated with namespace billing via labels and a crawler. Migration takes months per team, some high-traffic apps keep dedicated clusters, and AWS VPC/IP quotas bite.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 3:03Why 50 Kubernetes clusters
- 8:49Vision of shared clusters
- 11:40Challenges in consolidation
- 18:35Solution and benefits
- 19:39Costs and trade-offs
- 21:23Project timeline and migration
- 26:47Q&A session
related talks
36mOptimizing Resource Usage in Kubernetes
47mPostmortem: A Modern Approach to Managing Kubernetes Clusters
37mTenant Autonomy & Isolation In Multi-Tenant Kubernetes Clusters - A Comprehensive Guide
26mMulti-Tenant vs Micro-Clusters in Kubernetes-Driven Platform Engineering
29mNavigating the Multitenancy Maze: Avoiding Kubernetes Antipattern Pitfalls
35mKubernetes journey
29mRunning Kubernetes on 'small scale' clusters - lessons learned
46mAdvanced Kubernetes: Lesson Learned From Building..