GitOps Approaches and Trade-offs
summary
Covers concrete GitOps decisions: choose trunk-based development over branch-per-environment, keep an environment folder per repo, use Helm or Kustomize for templating, and keep secrets out of Git with a secrets manager. Compares push vs pull deployment models and trade-offs (cross-target CI power vs pull’s cluster-side sync). Recommends automated validation and parallel tests, describes blue/green and 1% canary ramp to 100% for low blast radius, and flags scale pain: 400 clusters running four incompatible versions.
AI-written summary · about
chapters (15)
- 0:00Intro
- 3:35Repository Structure
- 5:34Alternative to Branch Per Environment
- 6:50Repositories
- 8:25Push vs Pull
- 12:38Automated Validation
- 16:15BlueGreen Deployment
- 18:15Canary Deployment
- 20:30Questions
- 21:10Automation
- 23:47PR Review
- 25:20Git Push vs Git Pull
- 26:23Maintenance Windows
- 29:35Best Pattern
- 32:00Triggers
related talks
26mGitOps: yea or nay?
35mGitOps - Operations by Pull Request
35mGitOps - the holy grail of devops
06mGitOps - At a Glance
47mGitOps - Using Git as your source of truth for build, deploy and observability
15mGitOps Use Cases & Best Practices Com...
34mGitOps Is Likely More Than You Think It Is
55mGitOps, Fostering Next-Generation Operations Teams
