Argo CD Documentation

What Argo CD is

Argo CD describes itself as a declarative, GitOps continuous delivery tool for Kubernetes. It runs as a controller inside your cluster, watches one or more Git repositories, and continuously compares what Git says should be running with what is actually running. When the two differ, the application is marked OutOfSync, and Argo CD can bring the cluster back in line automatically or wait for someone to press sync. It is part of the Argo project, which joined the CNCF in March 2020 and reached Graduated status in December 2022.

What the docs cover

• Understand the basics and core concepts: applications, projects, sync status, health status and the idea of Git as the single source of truth.
• Getting started: installing Argo CD into its own namespace, installing the CLI, reaching the UI, logging in, registering a cluster, creating an application from a Git repository and syncing it.
• User guide: the manifest formats it understands (Kustomize, Helm charts, Jsonnet, plain YAML and config management plugins), sync options, sync waves and hooks, and multi-cluster deployments.
• Operator manual: SSO with OIDC, LDAP and SAML, RBAC and multi-tenancy, high availability, metrics, notifications and upgrade notes between versions.

Is it worth learning?

If you work with Kubernetes, yes. GitOps has become a common way for platform teams to deploy, and Argo CD is one of the most widely used GitOps tools. Learning it teaches you more than one product: pull based delivery, drift detection, and why "someone ran kubectl apply from a laptop" is exactly the problem it removes.

Prerequisites and time

You need a working Kubernetes cluster (a local kind cluster is fine), kubectl, and a Git repository with some manifests in it. Comfort with Deployments, Services and namespaces matters more than any Argo knowledge. The getting started guide takes an evening. Adding a Helm chart, a second environment through Kustomize, and SSO or RBAC takes a weekend or two.

Free or paid?

Argo CD is free and open source. Some vendors offer hosted versions; the docs cover the open source project.

Common questions

Does Argo CD replace my CI pipeline? No. CI still builds and tests your images. Argo CD handles the deploy step by watching Git, so CI usually ends by updating an image tag in the config repository.

Which docs version should I read? The stable link tracks the latest release. Check the version selector if your cluster runs an older Argo CD, and read the upgrade notes before moving between major versions.

What can I do after it? Deploy an application from Git, manage several environments from one repository, spot and fix drift, and explain the GitOps model clearly to a teammate.

Best for: DevOps, platform and backend engineers deploying to Kubernetes who want repeatable, auditable releases.