argoproj/argo-cd

Argo CD is a declarative GitOps continuous delivery tool for Kubernetes: application definitions, configuration and environments live in version control, and deployment and lifecycle management are meant to be automated and auditable. It fits teams already running Kubernetes who want cluster state driven from a Git repository rather than from imperative pipeline steps.

What changes in the workflow

Instead of a CI pipeline pushing manifests to a cluster, the cluster-side Argo CD component continuously compares the desired state in Git with what is actually running and reconciles the two. That means a Git commit becomes the deployment trigger and the reviewable record of intent, while drift between cluster and repository becomes visible rather than silent. The README frames this around two principles: declarative, version-controlled definitions, and automated, auditable deployment and lifecycle management declarative GitOps continuous delivery tool.

How it is used

The project ships a UI (shown in its demo GIF and a linked video) and a hosted live demo, so operators can inspect application health and sync status rather than reading logs. A Helm chart is published on Artifact Hub, which is one documented installation path alongside the manifests and CLI described in the full documentation Helm chart listing. The README also points to a user list for examples of organizations running it.

A common pattern described in the linked materials is managing multiple clusters from a control-plane installation, including temporary preview environments created per pull request. That is a fit argument, not a requirement: the core mode is a single installation reconciling one or more clusters.

Requirements and caveats

This is Kubernetes-specific software; it assumes a cluster to install into and Git-hosted declarative configuration to track. The supplied material does not document supported Kubernetes versions, upgrade steps or rollback behavior, so those should be checked in the full documentation complete documentation before committing production workloads. Argo CD itself is privileged control-plane software, so how it is isolated matters.

A 2024 Hacker News thread discussed a Redis cache deployed by Argo CD using risky or missing cryptographic algorithms HN discussion. One commenter noted the Helm chart includes a network policy that may mitigate exposure depending on the CNI, and suggested running Argo CD on a dedicated cluster as defense in depth; another argued the Redis instance is internal-only. These are unverified opinions about an older version, not a current assessment, but they illustrate why network isolation of the control plane deserves attention.

The code is Apache-2.0 licensed.