Argo CD v3.3.4 released on 16-03-2026
Argo CD v3.3.4 is out now. Operators can install it in both non‑HA and HA modes using the supplied release manifests, and all container images and CLI binaries for this release are signed with cosign with provenance generated to SLSA Level 3.
See the install manifests on GitHub, the operator docs for signed release assets and the release blog post and changelog compare for full details and verification instructions: installation manifests, signed‑release‑assets docs, release blog post and changelog compare.
What’s in this release
- Quick start and installation: non‑HA and HA install manifests provided; apply with server-side apply and –force-conflicts (non‑HA: https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.4/manifests/install.yaml, HA: https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.4/manifests/ha/install.yaml).
- Signed images and provenance: all Argo CD container images for v3.3.4 are signed with cosign and provenance is generated for container images and CLI binaries meeting SLSA Level 3; operator docs explain how to verify signatures.
- Changelog highlights and fixes: added missing git‑lfs installer checksum for ppc64le, skipped token refresh threshold parsing in unrelated components, documentation clarification on cluster version impacts for ClusterGenerator/CMP Plugins and migration, and an otel‑sdk bump. Full changelog: compare v3.3.3…v3.3.4.
Upgrade notes
- If you are moving between minor versions, follow the official upgrading documentation: see the upgrade overview before you proceed.
- Review the full changelog compare and the release metadata for details and any component-specific notes before upgrading.
Share your experience upgrading to v3.3.4 — report issues or notes on the project’s GitHub or drop a comment with what worked and what didn’t.
