GitLab as Cloud Native Complex Suite Made Simple with Helm
summary
GitLab’s Helm packaging is a tightly orchestrated suite: five external dependencies (some forked), about 6,000 lines of rendered output from roughly 40+ templates, effectively spitting out 19 charts in one. Goals are one-command installs on any cloud, maintainability, and component swapability; secrets never live in env vars — an init container injects them. Templates enforce deprecated-value checks and prevent known-bad configs. Adoption is slow but real: customers with 1,000–50,000 users run the charts in production.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:50Groundwork
- 1:20Scale
- 4:30Not everybody understands
- 6:03The challenge
- 6:58Why Cloud Native
- 8:06Why GitLab
- 9:17Targets
- 12:00Templating
- 15:37Templates
- 21:22Global Values
- 24:20Containerization
- 26:22Thank you
- 27:32QA
related talks
52mFrom 0 to Continuous Deployments with Kubernetes, Helm and GitLab
18mMulti-environment deployment for K8s-based microservice arch
32mManaging Helm Deployments with Gitops at CERN
26mRunning GitLab and GitLab CI in Kubernetes for the Enterprise
36mDelve into Helm: Advanced DevOps [I]
34mOne Chart to Rule Them All: Continuous Deployment with Helm at Ticketmaster
35mOptimizing Kubernetes Deployments with Helm
21mDriving Cultural Change to Improve Software Development and CI/CD