Argo CD v3.3.9 released on 30-04-2026
Argo CD v3.3.9 is out now. Operators can apply the v3.3.9 manifests for either non‑HA or HA deployments using server-side kubectl apply with –force-conflicts, and all container images are signed with cosign with provenance artifacts meeting SLSA Level 3.
See the v3.3.9 release branch manifests on GitHub and consult the operator manual for signature verification, provenance checks and upgrade guidance.
What’s in this release
- Quick start manifests for non‑HA and HA installs served from the v3.3.9 release branch; example installs use: kubectl create namespace argocd and kubectl apply -n argocd –server-side –force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.9/manifests/install.yaml (non‑HA) or …/ha/install.yaml (HA).
- Signed releases and provenance: all Argo CD container images are signed with cosign and provenance artifacts are produced for container images and CLI binaries that meet SLSA Level 3; verification guidance is in the operator manual documentation.
- Changelog items and fixes cherry‑picked into 3.3.9, including: avoiding an error on a second delete operation; fixing a pod-logs viewer crash from stale container indices; preventing ApplicationSet DuckType generator panics on non-string values; caching ocimetadata to/from Redis; plus a documentation correction for progressive sync version.
Upgrade notes
- If you are moving between minor versions, read the operator upgrade documentation before upgrading: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/
- For rollback or detailed upgrade procedures, follow the operator manual and the project’s upgrade guidance rather than applying changes blindly.
Share how the upgrade went and any issues you encounter on the project’s GitHub or community channels — feedback helps catch regressions and improve future patch releases.
