Canonical GitOps
summary
Argues for canonical GitOps: one deployment manifest plus an environment contract rather than many overlays. Shows a Pulumi-based platform that installs a Pulumi operator and a Stack CRD which pulls a Git repo, applies config (domain, min/max replicas) and reconciles; demo changes an image and scales replicas from 2 to 4 successfully. Compares alternatives: Flux/Argo directory overlays, Kyverno mutation, or custom operator. Recommends avoid overlays, use single deployment manifest and Pulumi operator/Stack CRD for branch-based promotion.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:24David Flanagan
- 1:22Kubernetes Conference
- 2:20The Law of Demeter
- 3:26Traditional Ci Cd Systems
- 6:0812-Factor Manifesto
- 6:50How Do We Handle Multi-Environment Get Ops
- 9:42Multi-Environment Example
- 10:12Directory Approach
- 11:11Branching Model
- 12:45Tools
- 21:26Deployment
- 25:11Resync Interval
- 33:34Final Tips
related talks
23mCanonical GitOps
26mGitOps Lifecycle Management
29mThe Evolution of GitOps in Platform Engineering
30mGitOps: Keeping It Light, Bright, and Deployed Right with OpenShift!
06mGitOps - At a Glance
28mManaging GitOps as a Platform Service
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
07mIntroduction to GitOps