
Argo CD — A GitOps CD controller for Kubernetes that syncs live cluster state from Git and flags drift automatically.
What it is
Argo CD is a free, open-source declarative GitOps continuous delivery tool for Kubernetes - an in-cluster controller that watches Git repositories and keeps deployed applications synced, healthy and auditable.
Editor's review
Long-form introduction by the BetterPicker editors · checked against the official site · Oct 23, 2026
Argo CD has become the default answer for Kubernetes teams that want deployments driven from Git rather than from CI jobs shelling into clusters with long-lived credentials. It is a declarative GitOps continuous delivery controller: point it at a Git repository holding Kustomize, Helm, Jsonnet or plain YAML manifests, and it continuously compares what the repository declares against what the cluster actually runs, visualizing the diff and syncing live state back to the desired state, automatically or on demand. Because the controller runs inside the cluster, external build systems no longer need cluster credentials, and every change carries Git's history, review trail and one-commit rollback. Setup walkthroughs consistently present the real-time UI, drift detection and self-healing as the payoff, and reviewers note the model asks for real workflow change in return: auto-sync, pruning and self-heal are opt-in rather than defaults, sync follows a polling interval unless you wire webhooks, and the tool governs only Kubernetes delivery, not the build pipeline. It is free and open source under the Apache-2.0 license, developed within the CNCF's Argo project, and installs into any conformant cluster from a single manifest or Helm chart; the current release line is 3.5.
What it does well
Git becomes the source of truth: application definitions live in version control, manual kubectl edits get flagged as drift and can be reverted automatically, and disaster recovery reduces to pointing a fresh cluster at the repository.
A pull model that tightens security: only the in-cluster controller applies changes, so CI systems and engineers need Git access rather than cluster credentials, while SSO (OIDC, SAML 2.0, LDAP), RBAC policies and AppProjects structure multi-team access.
Real-time delivery visibility: the web UI renders each application's resource tree with health and sync status, sync and rollback hooks support blue-green and canary rollouts, and webhooks, an API and Prometheus metrics plug it into surrounding automation.
Who it's for
Platform, SRE and DevOps teams running more than a toy Kubernetes estate - multiple environments, multiple clusters or multiple teams - who want deployment changes to flow through pull requests and stay auditable. Teams that already practice code review will feel at home, and ApplicationSets plus kustomize overlays give a structured answer for promoting manifests from dev to staging to production. If your workloads are not on Kubernetes, or your team cannot commit to a Git-first change process, look elsewhere first.
Where it falls short
Kubernetes only: it automates delivery to clusters, not builds or tests - you keep Jenkins, GitLab CI or GitHub Actions for CI, and non-Kubernetes targets need other tooling.
Cautious defaults add friction: automatic sync, pruning and self-healing ship switched off, and the polling loop checks on an interval unless webhooks are configured, so a naive install feels less immediate than a push pipeline.
A paradigm with upkeep: the GitOps discipline of separate config repositories, PR flow and overlay layout takes real onboarding, CRD fields evolve between releases, and because Argo CD holds the power to change clusters, its own RBAC and upgrade hygiene need deliberate care.
Specs at a glance
Facts from the official site · not editorial opinion
| Latest version | 3.5.6 |
|---|---|
| Price | Free; open source with no paid tiers |
| Platforms | Runs in any Kubernetes cluster; web UI and CLI available for macOS, Linux and Windows |
| Open source | Yes - Apache-2.0 (CNCF Argo project) |
| Core capability | Declarative GitOps CD controller that syncs Git-declared state to clusters with drift detection and health status |
| Integrations | Kustomize, Helm, Jsonnet and plain YAML sources; SSO via OIDC, SAML 2.0 and LDAP; webhooks for GitHub, GitLab and Bitbucket; Prometheus metrics |
| Best for | Platform and DevOps teams managing Kubernetes deployments across environments from audited Git repositories |
Frequently asked questions
▸Is Argo CD free?
Yes. Argo CD is open source under the Apache-2.0 license and is developed as part of the CNCF Argo project. Everything needed to run it - controller, UI and CLI - is free; commercial support and managed distributions exist from third-party vendors if you want them.
▸Does Argo CD replace Jenkins or GitLab CI?
No. It covers the delivery half: getting tested, built images into clusters as declared in Git. You still keep a CI system for building and testing code, and the recommended pattern is CI updating a config repository that Argo CD then syncs to clusters.
▸How does Argo CD handle dev, staging and production environments?
Common patterns are kustomize overlays over a shared base or per-environment values in Helm, promoted by merging changes between directories or branches. ApplicationSets can template applications across many clusters, and AppProjects scope who may deploy what and where.
▸How does Argo CD compare with Flux CD?
Both are open-source GitOps controllers for Kubernetes built on the same principles. Reviewers generally point to Argo CD's web UI, application model and multi-tenancy as its strengths, while Flux is often described as lighter weight and more modular; teams choose based on workflow and operating preferences.
Video reviews
4 review videos aggregated · praise and criticism included alike · click through to the original video
Channels that covered it
Channels are aggregated as sources only — we don’t rate creators
Related tools
Where to go next
External links open in a new tab; external content is independent of this site.
Link down? Every object page is re-checked monthly.





