Multi-environment deployment for K8s-based microservice arch
summary
Helm umbrella charts bundle dozens of microservices with per-customer values.yaml so product versions map to specific dependency versions and configs, enabling per-customer installs. GitLab CI/CD uses downstream pipelines to auto-deploy tagged service images into Dev and then QA, with deployment pipelines creating new product chart tags; a release manager still approves final product releases. Flyway runs DB migrations inside containers. Centralized single deploy repository holds cluster secrets and configs, using Helm umbrella charts, GitLab downstream pipelines, and automatic rollbacks as safety nets.
AI-written summary · about
chapters (9)
- 0:00Introduction to multi-environment K8s
- 1:45Challenges in microservice deployment
- 3:30Why we chose Helm charts
- 5:16Automatic rollbacks with Helm
- 7:26Microservice versioning process
- 9:11Testing single services vs product
- 10:35GitLab CI/CD integration
- 12:44Customer installation process
- 13:51Q&A on versioning and migrations
related talks
52mFrom 0 to Continuous Deployments with Kubernetes, Helm and GitLab
34mOne Chart to Rule Them All: Continuous Deployment with Helm at Ticketmaster
31mGitLab as Cloud Native Complex Suite Made Simple with Helm
35mOptimizing Kubernetes Deployments with Helm
40mMicroservice Continuous Delivery
32mManaging Helm Deployments with Gitops at CERN
37mDesigning Cloud Ready Applications
37mAutomated Provisioning using HELM charts on Kubernetes