Migrating from VMs to K8s
summary
A small startup migrates incrementally from long‑running EC2 VMs to Docker containers on EKS, starting with a low‑risk service then moving a memory‑hungry analytics service and auth service; cluster uses two EC2 worker nodes with four replicas per deployment and rolling updates, CI via CircleCI, infra built with Terraform and Chef, local development on a hybrid Vagrant + Docker Compose workflow, deploy scripts ~47 lines, DNS proxying / virtual‑host fallbacks protect traffic, and DB migrations run as ephemeral Kubernetes jobs.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:42Introductions
- 1:47Our Architecture
- 3:17Kubernetes
- 5:47You can do it too
- 10:01The criteria
- 14:13Team first
- 16:20Documentation
- 19:42K8 vs Tesla
- 21:10Scripting
- 22:50Big Scripts
- 24:46Communication
- 27:29Virtual Hosts
- 28:14Whats Next
- 37:40CICD
- 40:05Future Work
- 44:17Wrap Up
related talks
01h 25mTutorial: Migration 101: From VMs to Kubernetes
36mMigrating from kOps to EKS with Minimal Developer Involvement
33mNavigating the Seas of Transformation: Migrating from EC2 to Kubernetes
29mFrom EC2 to Kubernetes Takeaways from a Brownfield Migration
49mHardware to AWS, EC2 to EKS: Two Years, Two Epic Migrations
35mKubernetes journey
31mMigrating Legacy Infrastructure to Kubernetes: Olark’s Lessons From the Trenches
23mParadox's EKS Migration