Beyond Patterns and Principles
summary
Argues that GitOps is about declarative desired state plus agents that pull and repair continuously, not marketing buzz. Shows a real cluster built from Bicep with two repos (AKs bicep and cluster), Flux installing apps, Helm releases, AKS, Prometheus/Grafana/Dex for monitoring, and DSC/LCM acting like a pull agent. Notes only three widely known GitOps agents (Flux, Argo CD, Fleet), attempts an HPA scaling demo to five pods that mostly succeeds but proves flaky, and recommends continuous reconciliation as the core win.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:11What is GitOps
- 3:44Agile DevOps history
- 8:27GitOps and OpenGitOps
- 9:30GitOps principles vs culture
- 10:35Desired state in GitOps
- 13:26Agents and reconciliation
- 14:52Pull vs push agents
- 16:14GitOps and control theory
- 23:22GitOps tools and IaC
- 28:46Radius and Terraform alternatives
- 31:43CD tools and GitOps
- 35:17Flux Argo CD Fleet
- 38:53GitOps demo with Flux
- 1:09:23GitOps best practices
- 1:22:25Change management in GitOps
- 1:26:35Q&A
related talks
26mGitOps: yea or nay?
23mGitOps: yea or nay?
09mOpening and Welcome
34mGitOps Is Likely More Than You Think It Is
56mNavigating the GitOps ecosystem: The principles and in-depth look at Argo and Flux
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
45mGitops: The Kubernetes way
22mPush to Prod: GitOps Workflows on k8s with FluxCD