ArgoCD
ArgoCD is a declarative, GitOps continuous delivery tool for Kubernetes. It watches Git (or Helm/OCI sources), compares desired state to the cluster, and syncs drift—manually or automatically. Use this section to go from a working install to production-ready application management.
When to use ArgoCD
Choose ArgoCD when you want:
- A UI and CLI for application health, sync status, and rollback
- First-class support for Application and AppProject CRDs
- Clear separation of who can deploy what via Projects
- Multi-cluster delivery with a single control plane
If you prefer a controller-native toolkit with less UI focus, see Flux. For the shared model both tools implement, start with GitOps principles.
How ArgoCD works
ArgoCD continuously reconciles. You change manifests in Git; the controller detects the difference and applies it according to the Application’s sync policy. That pull-based loop is the core of GitOps CD—CI builds and tests; ArgoCD owns cluster state.
What you’ll learn
| Guide | What it covers |
|---|---|
| Setup & Configuration | Install ArgoCD, expose the UI/API, connect repositories, and bootstrap the control plane |
| Applications & Projects | Define Application CRDs, organize with AppProjects, and structure multi-app delivery |
| Sync Policies | Automated sync, prune, self-heal, sync windows, hooks, and safe rollout controls |
Suggested path
- Install — Follow Setup & Configuration until you can sync a sample Application.
- Model apps — Use Applications & Projects to mirror how your teams and environments are organized.
- Harden delivery — Apply Sync Policies so production updates are intentional, auditable, and reversible.
Related guides
- GitOps repository structure — how to lay out manifests ArgoCD should watch
- Environment promotion — promote changes across environments with Git
- Helm with GitOps — charts and values under ArgoCD
- CI/CD integration — keep pipelines focused on build/test; leave deploy to ArgoCD
FAQ
Is ArgoCD a CI tool?
No. ArgoCD is continuous delivery for Kubernetes. Build, test, and image push stay in CI (GitHub Actions, GitLab CI, etc.); ArgoCD reconciles the cluster from Git.
Do I need the UI?
No. Everything can be declarative via Application manifests and the CLI. The UI helps with visibility and incident response.
Can one ArgoCD manage many clusters?
Yes. Register destination clusters and point Applications at them. Use Projects to limit which teams can target which clusters and namespaces.