Argo CD: GitOps delivery for Kubernetes, three patched release lines, and a tutorial list older than v3

Version controlled definitions as the source of truth

Argo CD describes itself as a declarative GitOps continuous delivery tool for Kubernetes. Its rationale fits in two lines. First, application definitions, configurations and environments should be declarative and version controlled. Second, application deployment and lifecycle management should be automated, auditable and easy to understand. In practice that means the desired state of what runs in your clusters lives in a Git repository, and Argo CD is the component that reconciles the clusters with it, so a change to the repository is how a deployment happens. The project is written in Go, licensed under Apache-2.0 and developed on the master branch, with documentation at argo-cd.readthedocs.io and a public live demo at cd.apps.argoproj.io that lets you click through the interface before installing anything.

Three minor lines patched on the same afternoon

On 2026-11-02 the project tagged v3.5.7 at 20:14 UTC, v3.4.13 at 20:15 UTC and v3.3.19 at 20:18 UTC. Three supported minor lines received patch releases within four minutes of each other, and the last push to master landed earlier that day. This is a project under heavy, coordinated maintenance.

For operators the consequence is that the version you run matters more than the word latest. A fix shipped in a coordinated batch reaches all three lines, but anything older than 3.3 was not part of that batch. Pin a minor line deliberately, watch the releases page for that line, and plan your minor upgrades before your line drops out of the set that receives patches.

Kubernetes is the only stated target

The repository description is Declarative Continuous Deployment for Kubernetes, and every part of the README framing assumes Kubernetes clusters as the place applications run. If your workloads live on plain virtual machines, serverless platforms or bare metal hosts without Kubernetes, Argo CD does not describe a way to deploy to them directly.

The linked talks show how people stretch the model: several pair Argo CD with Crossplane, under titles such as How to Apply GitOps to Everything, so that external infrastructure is represented as Kubernetes resources and then managed the same way. That is an extra control plane to run and learn. The practical consequence is that adopting Argo CD for a mixed estate means either moving workloads onto Kubernetes or adding a tool like Crossplane in between.

Delivery only, so builds and tests live in another system

Argo CD is positioned as continuous delivery. Its own description covers declarative application definitions and automated, auditable deployment; nothing in it covers compiling code, running test suites or producing container images. The tutorials it links reflect that division of labour: one pairs it with CircleCI, another with Codefresh, and one compares Argo CD with Spinnaker, Jenkins X and Tekton.

For teams asking whether Argo CD replaces Jenkins, the honest reading is that it covers a different stage. You still need something to build and publish artifacts, and something to update the manifests in Git when a new image exists. The linked talk GitOps Without Pipelines With ArgoCD Image Updater points at a separate project for that second job, so budget for at least one more component beside Argo CD itself.

Installation is routed through the docs and a Helm chart

The repository front page does not carry a copy and paste install command. Instead it sends readers to the complete documentation at argo-cd.readthedocs.io and advertises a Helm chart published on Artifact Hub as argo/argo-cd. Teams that already manage cluster add-ons with Helm can install and upgrade Argo CD through that chart, while others follow the manifests and CLI instructions in the documentation. Among the linked guides, Setting up Argo CD with Helm and Deploy Argo CD with Ingress and TLS in Three Steps cover the two questions most installations hit first: how to install it reproducibly and how to expose the web interface securely. Pick one route and stick with it, since upgrades follow the same path you installed with.

Much of the linked reading predates the 3.x line

The Blogs and Presentations list is long and generous, but a good part of it is old. Linked posts carry dates in their URLs from 2020-12-03, 2020-12-17, 2021-05-06 and 2022-12-16, one guide targets IBM Multicloud Manager 3.1.2, and the Kubeflow entry points at documentation for Kubeflow v0-6. Current releases are on the 3.3, 3.4 and 3.5 lines.

The consequence for newcomers is that following a linked tutorial step by step can mean following an interface, flag or manifest layout that has since changed. Use these talks for concepts such as preview environments built from pull requests, ApplicationSet driven automation, or progressive delivery with Argo Rollouts and Istio, and take the concrete commands from the current documentation.

Supply chain checks and a scheduled community

The README badges point to SLSA provenance for releases, an OpenSSF Best Practices entry, an OpenSSF Scorecard, Codecov coverage and an integration test workflow on GitHub Actions. Those are signals that the release process is checked, which matters for a tool that holds credentials to deploy into your clusters.

The project runs on a regular calendar: contributor office hours every Thursday, a user community meeting on the first Wednesday of each month, questions in GitHub Discussions and chat in the #argo-cd channel on the Argo project Slack. Participation is governed by the CNCF Code of Conduct, and organisations running it can add themselves to USERS.md, the official user list kept in the repository.

Editorial conclusion

Argo CD fits teams that already run Kubernetes and want application definitions, configuration and environments kept declarative in version control, with deployment automated and auditable. It is the wrong tool if your targets are not Kubernetes clusters or if you are looking for a system that also builds and tests code. Before adopting it, decide which 3.x minor line you will track, install from the documentation at argo-cd.readthedocs.io or the argo/argo-cd Helm chart, and check any older tutorial against current docs.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes