Deploys from Git
The cluster follows a repository, and a change in Git is a deployment.
DevOps
Argo CD services for teams that deploy from Git
We have no published Argo CD build. We have shipped Docker deployments and Azure DevOps pipelines, and we show where Argo CD would take over the last step.
0Published builds on Argo CD
4Minor releases a year
3Most recent minor versions supported
0Fixes for versions older than that
What we build
What we would take on with Argo CD
Argo CD upgrades
Moves inside the three supported minor versions.
Clusters beside pipelines
Argo CD after the build, not in place of it.
Reviewable releases
Every release is a commit someone reviewed.
Architecture
Where Argo CD would sit
Argo CD after the build step
Build
Docker multi-stage buildTruckFleet Labs
Azure DevOpsHydrajaws, Verify Auto
Delivery
Argo CDWhere it would sit
Run
KubernetesCluster
Illustration. A dashed outline marks where the technology would sit. We have no published build on it.
Versions
How Argo CD is supported
The Argo CD release policy
Release cadenceA minor release four times a year, about every three months.
Support windowOnly the three most recent minor versions get patch releases.
End of lifeOlder versions receive no bug fixes or security updates.
Source: Argo CD documentation, release process and cadence, checked 4 November 2026. Minor releases target the first Tuesday of February, May, August and November.
Builds
The closest builds we can show you
Logistics, fleet operations
TruckFleet Labs
A Docker multi-stage build with Docker Compose behind a FastAPI back end.
38Drivers on the app by week three
Construction safety testing, United Kingdom
Hydrajaws Limited
Azure DevOps pipelines and environments rebuilt for stable releases.
500%Surge in potential clients
Fit check
When Argo CD is the right call
Pick Argo CD when
- You already run Kubernetes
- You want deployments reviewed as commits
- Several clusters must stay in step
Look elsewhere when
- You need a published Argo CD build to inspect, which we do not have
- A few services on one host, where Docker Compose is enough
- You have no cluster yet
Explore
Same job, other tools
Where we used it
Stack
What Argo CD usually sits beside
KubernetesDocker
Terraform
Azure
AWS
JenkinsFAQs
What buyers ask first
Which Argo CD versions are supported?
Only the three most recent minor versions get patch releases. Older versions are end of life and receive no bug fixes or security updates.
Do you have a published Argo CD build?
No. We say so on the first call and show the nearest work, which is Docker deployments and Azure DevOps pipelines.
How often does Argo CD release?
A minor release four times a year, about every three months, targeting the first Tuesday of February, May, August and November.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Tell us how you deploy to your cluster
Thirty minutes on your clusters, your repositories and your Argo CD version. No sales pitch.