We Broke Free From Cloud-Managed Kubernetes...
summary
Saxo Bank migrates from cloud-managed Kubernetes to on-prem using kubeadm + Cluster API on flatcar VMs atop VMware, and reports a compelling cost case (marketing claim of up to 80% cost reduction but recommends doing your own math). Major surprises: asymmetric routing and DNS behaviors force a custom operator for stretch clusters, patching external-dns/coreDNS, and heavy image bundling for airgapped sites. Management uses Helm, Kyverno and GitOps; capacity planning, monthly failover tests, and storage design prove crucial.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:28Leaving cloud-managed Kubernetes
- 4:14Kubernetes expectations
- 4:55Stretch cluster challenges
- 8:48DNS issues and fixes
- 12:01External access setup
- 13:04Cluster management with CAPI
- 15:36Management hierarchy automation
- 16:57Migration progress and DX
- 18:21GitOps migration demo
- 19:28Beyond cost savings
- 20:31Lessons and future
- 22:42Recommend this approach?
- 23:45Closing and Q&A
related talks
25mBreaking Free From the Cloud: Banking on Self-Hosted Kubernetes
34mTaking Back Control: Building Cloud-Agnostic Container Platforms for Regulated Environments
28m03 Kubernetes Evolution, from the Hard Way to Managed Multi-cloud
19mBuilding an On-Premise Kubernetes...
49mThe state of on-prem Kubernetes
35mKubernetes journey
19mKeynote: From COBOL to Kubernetes: A 250 Year Old Bank's Cloud-Native Journey
26mIf You Build It, They Will Come - a Platform Modernization Journey