Flux vs Argo CD
Choosing your GitOps tool.
Flux and Argo CD are the two graduated CNCF GitOps projects, and the choice is about fit, not correctness. Flux is modular, API-first, and Kubernetes-idiomatic: composable controllers, everything a CRD, no default UI, multi-tenancy through native RBAC and impersonation, and notably strong built-in supply-chain verification. Argo CD is a richer application with a first-class UI, a built-in multi-tenant model (projects, RBAC, SSO), and ApplicationSets — more batteries included, more of a central platform.
Same stakes, different ergonomics
Whichever you choose, the security work is identical and non-negotiable: Git becomes your deploy authority, the tool holds cluster credentials, and you must protect the repo (reviews, signed commits), scope the controller’s permissions, verify what it pulls, keep secrets encrypted, and pair with admission policy. Many organizations run one or the other happily; some run both for different fleets. Decide on ergonomics and features, then apply the same GitOps hardening either way.