Canonical GitOps
summary
Claims that a single deployment description should live next to each service and that applying the Law of Demeter to GitOps removes overlay coupling. Compares three models—directory, branch, repository—notes a Flux issue with 56 thumbs up and persistent confusion. Shows a working proof of concept using TypeScript and the Pulumi operator inside Kubernetes to read a ConfigMap contract, render manifests (ingress, service, HPA), and deploy cert-manager, Contour and Red Panda. Promotes Canonical GitOps with branch-based promotion and optional mutating-admission or operator augmentation; the demo runs and produces reproducible environment URLs.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 1:26Law of Demeter explained
- 4:53Traditional CI/CD workflows
- 7:43Multiple environment GitOps options
- 11:17Challenges with directory approach
- 13:01Canonical GitOps solution
- 16:37Platform and application separation
- 19:01Implementation with Pulumi
- 20:24Quick tips for GitOps
- 21:07Summary and Q&A
