The Journey of Migrating 2500 Apps to Multi-Cluster Kubernetes and Zero Trust Istio
summary
Migrating ~2,500 apps into a multi-cluster Kubernetes estate runs on 40 clusters (≈20 prod, 20 dev), ~20,000 containers, 4,500 deployments and 1.7 TB/day of logs; platform chooses kops over managed EKS, provides soft multitenancy via namespaces and a single Git repo with templated Helm charts (zp-app, zp-cronjob), uses Istio + GlooMesh for zero‑trust, and fixes outages by switching to CoreDNS node‑local, trimming sidecar visibility and tuning node‑delete delays so the setup runs reliably at scale.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:08Why multi-cluster Kubernetes
- 3:36Infrastructure metrics and AWS setup
- 4:42AWS account and VPC strategy
- 10:25Multi-cluster architecture decision
- 12:36Kubernetes distribution choice
- 14:20Soft multitenancy with namespaces
- 16:03Istio for zero trust
- 22:07Migration challenges and fixes
- 28:55Future platform plans
- 32:04Istio ambient mesh
- 33:47Q&A
related talks
35mKubernetes journey
20mKeynote: The Challenges of Migrating 150+ Microservices to Kubernetes
24mIstio in Production: Expected Value, Results, and Effort
37mOne Cluster to Rule Them All - Multi-Tenancy for 1k Users
35mClusters as Cattle: How to Seamlessly Migrate Apps Across Kubernetes Clusters
33mNavigating the Seas of Transformation: Migrating from EC2 to Kubernetes
38mThe Good, the Bad & the Ugly of Migrating Hundreds of Legacy Applications to Kubernetes
38mBuilding the Perfect Infrastructure with Kubernetes