Argo CD v3.3.8 released on 21-04-2026
Argo CD v3.3.8 is out now. It includes immediate installation manifests for non‑HA and HA deployments, signed container images and provenance artifacts, plus a set of bug fixes addressing automatic-refresh behaviour, core-mode sync failures and AppSet status defaults.
Follow the Quick Start manifests on GitHub to install (server-side apply with –force-conflicts), consult the signed release assets documentation to verify images and binaries, and see the full changelog for complete details.
What’s in this release
- Quick Start: create the argocd namespace and apply the appropriate manifest with server-side apply and –force-conflicts (non‑HA: https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.8/manifests/install.yaml; HA: https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.8/manifests/ha/install.yaml).
- Release signatures & provenance: all container images for v3.3.8 are signed with cosign and provenance artifacts are produced for images and CLI binaries meeting SLSA Level 3 (see signed release assets docs).
- Notable fixes: revert of the automatic-refreshes change; fix for appcontroller in core mode failing to sync when server.secretKey is missing; AppSet resource status default changed to 5000, plus other bug fixes (full changelog available).
Upgrade notes
- If you are upgrading from a different minor version, read the official upgrading documentation before proceeding: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/
- If you need to review or roll back changes, consult the full changelog and compare view between v3.3.7 and v3.3.8: https://github.com/argoproj/argo-cd/compare/v3.3.7…v3.3.8
Share your experience with the upgrade or installation — notes on any unexpected behaviour are welcome.
