Argo and Flux are in a Kargo — which one sinks?
summary
Compares Argo CD (central control plane with UI and RBAC) and Flux CD (per-cluster controllers with native Helm/Kustomize/Terraform support) and introduces Flamingo, which combines Argo CD’s UI with Flux controllers. Demonstrates on GKE: install Flamingo, deploy two apps using different reconciliation engines, then use Kargo v0.6 to promote an nginx image by writing promotion commits to Git (updating overlays) and triggering Argo sync to move the image from dev→test. Notes that the demo tooling works but Flamingo and Kargo are not yet production-mature.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:07GitOps definition
- 3:36Push vs Pull in GitOps
- 8:57Argo CD and Flux CD
- 13:11Argo vs Flux choice
- 14:14Flamingo demo
- 20:35GitOps environments
- 24:50Kargo demo
- 35:47Conclusion
- 36:50Q&A
related talks
18mTwo GitOps Titans, One Powerful Solution: Flamingo (Flux + Argo)!
56mNavigating the GitOps ecosystem: The principles and in-depth look at Argo and Flux
26mGitOps Simplified
14mLightning Talk: Progressive Infrastructure Delivery Using Kargo and Argo CD
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes
33mProgressive Infrastructure Delivery using Kargo and Argo CD
06mArgo CD and Kubernetes from event based to microservices
32mIntroduction to ArgoCD