Skip to content
Documentation Background

Argo CD

Argo CD is a declarative GitOps continuous delivery controller for Kubernetes. It compares the live state of applications in one or many clusters with the manifests in Git, reports any difference, and brings the cluster back to the declared state. It is a CNCF graduated project.


CapabilityDetail
One unit per applicationAn Application groups the Deployments, Services, and other objects of a workload, so it is deployed, versioned, and managed as a whole
Multi-cluster deliveryOne control plane deploys to many Kubernetes clusters
Drift detectionLive state is compared continuously, and differences are shown in the UI and API
Sync controlManual approval, or automated sync with pruning and self-healing
Manifest toolingPlain YAML, Helm, Kustomize, Jsonnet, and custom plugins
Access controlRBAC, local accounts, and single sign-on through OIDC providers or the bundled Dex server
InterfacesWeb UI, CLI, and a REST and gRPC API
Rollback and recoveryA rollback is a revert in Git. A lost cluster is rebuilt by installing Argo CD and pointing it at the same repository

  • Raw manifests first. Argo CD works on Kubernetes YAML and behaves as much like kubectl as it can.
  • Render, then apply. Helm and Kustomize output is rendered to plain manifests before it is applied. For Helm this uses helm template, so helm ls shows no releases for charts that Argo CD manages. In exchange, Argo CD can diff a Helm application against live state like any other.
  • Continuous reconciliation. Controllers pull declarations from Git on a timer or on a webhook and align running state with them.
  • Declarative all the way down. Applications, projects, and Argo CD’s own settings are Kubernetes objects, so the installation can live in Git too.
flowchart LR
    Git["Git or Helm repository"] --> Repo["Repo server<br/>renders manifests"]
    Repo --> Ctrl["Application controller<br/>compares and syncs"]
    Ctrl --> Cluster["Target clusters"]
    User["UI, CLI, API"] --> API["API server"]
    API --> Ctrl

Flux and Argo CD are the two leading open-source GitOps controllers. They solve the same problem with different designs.

AspectArgo CDFlux
DesignA complete product with a UI, API, and RBACComposable controllers (the GitOps Toolkit), each doing one job
HelmRenders with helm template, applies raw YAMLInstalls charts through the Helm SDK as Helm releases
helm lsShows nothing for Argo CD-managed chartsLists the releases
InterfaceBuilt-in web UI, RBAC, and multi-tenancyPrimarily CLI and API driven, with UIs added by other projects

Neither is strictly better. Argo CD suits teams that want a visual application view and built-in access control. Flux suits teams that prefer to assemble their own tooling from smaller parts.


Argo CD is one of four related projects. They work together or on their own.

ProjectRole
Argo WorkflowsWorkflow engine for parallel jobs and pipelines on Kubernetes, used for data pipelines and CI
Argo CDGitOps continuous delivery
Argo RolloutsProgressive delivery with canary and blue-green strategies, automated analysis, and rollback
Argo EventsEvent-driven triggers for Kubernetes objects, workflows, and functions

You should be comfortable with:


The pages are written to be read in this order. Each stage builds on the one before it.

StageReadYou will be able to
1. Get startedArchitecture, Installation and access, Web UI and CLI, Declarative configuration and APIExplain the components, install Argo CD, log in, and manage its settings as code
2. Deploy applicationsApplications, Rendering toolsDeploy a workload from Git, Helm, or Kustomize and delete it safely
3. Control how changes roll outSync policies and options, Phases, hooks, and waves, Diffing and ignore rules, Application health, Database schema walkthroughAutomate sync, order resources, silence false drift, and judge health
4. Scale to many clusters and teamsCluster management, Multi-tenancy and projects, App-of-apps and ApplicationSetsRegister clusters, isolate teams, and generate applications at scale
5. Secure itAccounts and RBAC, Single sign-on, TLS and repository credentials, Commit signing and sync impersonationLock down access, connect an identity provider, and protect Git credentials
6. Run it in productionCI integration and webhooks, Monitoring and notifications, High availability and scaling, Extending Argo CDConnect pipelines, watch the system, size it, and extend it
7. Put it togetherWalkthrough: from commit to productionRun a full pipeline from a merge to a reviewed production release
ReferenceTroubleshooting, CheatsheetDiagnose problems by symptom, and look up commands, annotations, and configuration keys