Argo CD v3.3.6 released on 27-03-2026
Argo CD v3.3.6 is out now. It supplies immediate install commands for both non‑HA and HA deployments and publishes signed container images with provenance for operators who need verifiable releases.
For full details, follow the quick start commands (non‑HA and HA), consult the operator‑manual on verifying signed release assets and read the full changelog and release blog on the project pages.
What’s in this release
- Quick start install commands: create the argocd namespace and apply the server‑side manifests with –force-conflicts. Non‑HA: kubectl apply -n argocd –server-side –force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.6/manifests/install.yaml; HA: use manifests/ha/install.yaml.
- Signed releases and provenance: all Argo CD container images are signed with cosign and provenance artifacts are generated for container images and CLI binaries that meet SLSA Level 3; see the operator‑manual for verification steps.
- Changelog and bug fixes: fixes include a controller diff detection bug during app normalization (commit 4a823fecf0c2…; cherry‑pick #27002) and a wrong installation id returned from cache (commit c5d7748f2e8…; cherry‑pick #26969). Full changelog: https://github.com/argoproj/argo-cd/compare/v3.3.5…v3.3.6
Upgrade notes
- If you’re moving between minor versions, read the official upgrading documentation before proceeding: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/
- If you need to revert, consult the GitHub compare (v3.3.5…v3.3.6) to identify the specific commits to roll back.
Share any comments on your upgrade or install experience — reports on verification steps and post‑upgrade behaviour are especially useful to the community.