How a Unicorn Migrated From an In-House Solution to Helm
summary
Migrates 400+ services from an in‑house Python CloudFormation generator into Helm, keeping AWS EKS, Argo CD and Jenkins pipelines (images to ECR, charts to Artifactory). Builds a reusable base chart (charter) pattern split into focused base charts (HPA, ingress, secrets), integrates with Hugatka to emit values.yaml generator and ApplicationSet/service account artifacts, serves ~130 developers, preserves defaults while allowing overrides, and proves operational at scale (real‑time 50M decisions/day) — the migration works and speeds developer autonomy.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:15Talk overview
- 3:03Migration challenges
- 4:50Why Helm over in-house
- 7:16Developer autonomy vs standards
- 13:49Helm chart architecture
- 25:14Base chart explained
- 31:39CI/CD for Helm
- 33:27Helm with infrastructure
- 39:51Beyond single base chart
- 40:59Key takeaways
related talks
43mHow a Unicorn Migrated From an In-House Solution to Helm
34mOne Chart to Rule Them All: Continuous Deployment with Helm at Ticketmaster
32mHelm your way with Kubernetes
09mHow migrating from ECS to EKS supercharged our infrastructure
27mAre you Helming it the right way? Helm challenges and its solutions
29mHelm Your Way with Kubernetes
05mLightning Talk: New Helm Chart Installation Experience with Visual and Repeatable...
26mHelm your way with Kubernetes