Challenges of Migrating a High Traffic Mobile Game to Kubernetes
summary
Migration moves a high‑traffic mobile game from DigitalOcean VMs to EKS on AWS, replaces MySQL 5.7 → RDS MySQL 8 (hit io2 64k IOPS bottleneck, fixed by disabled sync_binlog during cutover), converts PHP‑FPM to containers with Helm, implements blue‑green deploys via GitHub Actions → ArgoCD, solves once‑per‑minute cron with Jenkins cron agents running hot images, replaces sharded Redis with a KeyDB cluster, lowers autoscale CPU threshold to 50% and achieves no‑downtime cutover and improved reliability.
AI-written summary · about
chapters (12)
- 0:00Game migration challenges
- 1:48Initial infrastructure
- 7:21Planning Kubernetes migration
- 10:51Pre-migration technical challenges
- 13:42Cron jobs in Kubernetes
- 16:54Jenkins to GitHub Actions
- 18:39Blue-green deployments
- 20:44Autoscaling PHP in Kubernetes
- 23:15DNS and database migrations
- 26:08EKS security improvements
- 27:54Optimizing Redis with KDB
- 29:19Kubernetes migration benefits
related talks
24mMigration of NCSOFT Game Servers to Kubernetes
20mKeynote: The Challenges of Migrating 150+ Microservices to Kubernetes
33mNavigating the Seas of Transformation: Migrating from EC2 to Kubernetes
38mThe Good, the Bad & the Ugly of Migrating Hundreds of Legacy Applications to Kubernetes
28mMoving a Monolith from AWS EC2 to K8
38mThe Reality of Porting Kubernetes Apps Across Cloud Providers
32mMigrating 2 million CPU cores to Kubernetes
49mHardware to AWS, EC2 to EKS: Two Years, Two Epic Migrations