Migrating a Monolith to Kubernetes with Istio: Our Jou...
summary
Adobe migrates a legacy monolith into Ethos Kubernetes with Istio as the service mesh, moving from 80 clusters worldwide and 70 microservices to a single platform deployed via GitOps and completed within a year. Key wins: no downtime for final traffic cutover, consolidated SRE support, aggressive scale-in/out and cost savings. Concrete blockers and fixes include external-dns cross-namespace changes, Cilium CNI compatibility issues, HAProxy load randomness hotspots, certificate cross-namespace workarounds, and an SMTP workload kept on VMs due to client-IP preservation limits.
AI-written summary · about
chapters (10)
- 0:00Adobe monolith migration intro
- 3:17Why Kubernetes and Istio
- 6:27Migrating to companywide platform
- 7:09Istio implementation pitfalls
- 12:04Pitfalls beyond Istio
- 15:35Production service mesh tips
- 18:29Legacy constraints and workarounds
- 18:49Istio observability features
- 20:17Final migration benefits
- 22:46Ambient Mesh future
related talks
26mIstio Migration: 50k+ Pods, Minimal Impact, Lessons Learned
38mIstio as an enabler for migrating Monolithic apps to Microservices
24mFrom Monolith to Microservices: A Journey into the Mesh
54mTransform a Legacy Application with Kubernetes and Istio
46mIstioD - from microservices to monolithic
44mDocker, Kubernetes and Istio — Useful for My Monolith?
18mRe-Architecting Monoliths Into Kubernetes Microservices at Million-User Scale: Hard...
18mLessons from Scaling AI Powered Translation Services Using Istio