Navigating the GitOps ecosystem: The principles and in-depth look at Argo and Flux
summary
Compares concrete setups: Argo CD brings a full UI, Argo Events, application sets and built-in orchestration (demo deploys Argo to AKS and shows UI-driven sync, click-ops and manual overrides), while Flux is a lightweight set of Kubernetes controllers using the GitOps Toolkit (gotk), image automation and a smaller surface for external deps. Notes that many orgs disable Argo auto-reconcile at scale, initial Argo install needs Terraform for hardening, Flux ships in AKS, and open issues contrast (~3,000 Argo vs ~300 Flux).
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:09What is GitOps
- 3:17Declarative vs imperative
- 6:06GitOps workflow
- 9:03Developer perspective
- 12:13Team responsibilities
- 14:01Argo CD deep dive
- 21:06Argo CD challenges
- 23:11Argo CD demo
- 27:55Argo CD drift handling
- 30:00Flux introduction
- 32:46Flux architecture
- 35:14Flux benefits
- 37:46Flux UI and community
- 39:52Argo CD vs Flux
- 42:27Partial delegation
- 45:58GitSecOps
- 47:26Secrets management
- 48:34Argo CD security
- 50:17GitOps best practices
- 51:45Summary and future
- 54:59Q&A
related talks
26mGitOps Simplified
42mArgo and Flux are in a Kargo — which one sinks?
25mCI/CD with GitOps and AKS
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes
48mThe State of GitOps in 2021
31mLeveraging GitOps to wrangle your clusters and projects
07mIntroduction to GitOps
31mGitOps and Kubernetes: a Winning Combo