DevOps / GitOps Interview Questions
What is Flux CD and how does it differ from Argo CD?
Flux CD is a CNCF-graduated GitOps toolkit for Kubernetes. Unlike Argo CD — which ships as a relatively integrated platform with a built-in UI, Application model, and unified controller — Flux is composed of separate, independently deployable controllers, each managing a specific concern. You assemble the controllers you need and extend them without touching the others.
| Dimension | Flux CD | Argo CD |
|---|---|---|
| Architecture | Composable controllers (source, kustomize, helm, notification, image-automation) | Integrated platform with API server, repo server, application controller |
| UI | CLI-first; Weave GitOps is a separate optional UI | Built-in rich web UI with app graph and diff view |
| Application model | GitRepository + Kustomization CRs (composable) | Application CR (opinionated single resource) |
| Image automation | Built-in ImageRepository / ImagePolicy / ImageUpdateAutomation | Requires Argo CD Image Updater (separate tool) |
| Multi-tenancy | Namespace-scoped CRs; each team manages their own Flux CRs | AppProject model with centralised RBAC policy |
| Helm support | HelmRelease CR with native drift detection and remediation | Application source.helm with sync phases |
| CNCF status | Graduated (2022) | Graduated (2022) |
In practice: teams that prioritise a strong visual UI and centralised management tend to choose Argo CD. Teams that prefer composable building blocks, want to avoid centralised control-plane complexity, or need built-in image automation often choose Flux. Both are production-ready and widely deployed at scale.
What is the primary architectural difference between Flux CD and Argo CD?
Which capability is built into Flux CD but requires a separate add-on project with Argo CD?
More Related questions...
