Kustomizing Auto DevOps - an Extensible Deploy Stage
summary
Auto DevOps stays compatible while the deploy stage becomes declarative: the pipeline swaps Helm releases for Kustomize over Helm plus kpt, runs k3s in CI, and deploys nginx-ingress and podinfo as a composed package. kpt performs a kpt three-way merge so manual in-place edits (replica changes) survive upstream updates, and kpt live apply waits for pod readiness and prunes removed manifests. The result is seamless upgrade paths from imperative CI deploys to GitOps-style manifests.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:45About MSI Technologies
- 2:15Why Auto DevOps
- 3:07What Makes Our Platform Successful
- 8:02What is Auto DevOps
- 10:50Challenges with Auto DevOps
- 14:37Declarative Resource Management
- 17:17Imperative vs Declarative
- 19:05Customization
- 22:50Goals
- 25:49App Implementation
- 26:46Cimal Template
- 27:42CI Pipeline
- 29:21Pruning
- 29:50Annotations
- 30:37Customize
- 30:55Day 2 Operations
- 32:48Threeway Merge
- 37:10Customizing Service Name References
- 38:02GitLab Kubernetes Integration
- 39:18Techton
related talks
20mMulti-Stage Deployment Pipelines the GitOps Way
30mLet's Kustomize Our K8S Deployments with Style!
34mKustomize: Template-Free Configuration Customization for Kubernetes
06mMulti-Stage Deployment Pipelines the GitOps Way
07mNavigating Multi-stage Deployment Pipelines via the GitOps Approach
07mKustomize: Manage K8S manifests natively
57mGitOps: From Commit to Deploy
34mKustomize vs Helm - Civil War