Argo CD v3.3.9 released on 30-04-2026
Argo CD v3.3.9 is out now. Operators can bring up a single-instance or HA deployment quickly using the provided server-side install manifests and immediate kubectl commands.
See the release assets on GitHub (manifests and signed artifacts) and the project documentation for verification and upgrade guidance.
What’s in this release
- Quick start install commands for v3.3.9: create the argocd namespace and apply the non‑HA or HA manifests server-side with –force-conflicts (manifests hosted on raw.githubusercontent.com).
- All container images are signed with cosign and a provenance is generated for container images and CLI binaries that meet SLSA Level 3; documentation shows how to verify signatures and provenance.
- Cherry‑picked bug fixes addressing stability issues: avoid errors on a second delete operation; prevent pod logs viewer crashes on stale container indexes; fix ApplicationSet DuckType Generator panics on non‑string values; store/retrieve ocimetadata in the Redis cache; plus documentation and dependency updates.
Upgrade notes
- If you are upgrading across minor versions, read the official upgrading documentation before proceeding: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/
- Verify signed artifacts and provenance before upgrading; signed images and CLI binaries and guidance are available in the release assets and documentation: https://argo-cd.readthedocs.io/en/stable/operator-manual/signed-release-assets
Share any feedback or issues on the project’s GitHub and note your experience when testing the signed artifacts and install manifests.
