Moving to Kubernetes, or not?
summary
Company moves from container per VM to Kubernetes on GCP but discovers real work: Docker containers already run, Jenkins pipelines are tightly coupled to AWS, and redoing CI/CD takes weeks. Migration uses $300 GCP credit and still overruns; running Kubernetes against a largely containerized monolith exposes scaling and complexity mismatches. Concrete outcome: clusters and pipelines get built, cost and integration pain delay cutover, and the team decides only partial adoption is practical rather than a full lift-and-shift.
AI-written summary · about
related talks
05mJenkins in the Cloud
20mKeynote: The Challenges of Migrating 150+ Microservices to Kubernetes
38mThe Reality of Porting Kubernetes Apps Across Cloud Providers
37mBalancing Power and Pain: Moving a Startup From a PaaS to Kubernetes
45mLearning How to Pronounce Kubernetes to Production in 3 Months!
19mMigrating GitLab.com to Kubernetes: How Multiple Clusters Saved Cost
29mFrom EC2 to Kubernetes Takeaways from a Brownfield Migration
43mMoving the Unmovable: migrating from VMs to K8s