Argo CD v3.3.5 released on 25-03-2026
Argo CD v3.3.5 is out now. Operators and cluster administrators get immediate install options for Non‑HA and HA deployments, signed container images with provenance meeting SLSA Level 3, plus a set of cherry‑picked bug fixes and dependency updates.
Consult the official install manifests and the project documentation for installation, verification and upgrade details—see the GitHub manifests, the signed-release-assets docs and the operator manual upgrade overview.
What’s in this release
- Quick start: create the argocd namespace and apply the official manifests with server-side apply and –force-conflicts. Non‑HA: https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.5/manifests/install.yaml; HA: https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.5/manifests/ha/install.yaml
- Signed artifacts and provenance: all Argo CD container images are signed with cosign and provenance metadata is produced for container images and CLI binaries that meet SLSA Level 3—see the signed-release-assets documentation for verification steps.
- Bug fixes: clearer RollingSync step display when labels match no step; fixed container-finding logic for terminal sessions; resolved a stack overflow caused by circular ownerRefs in the resource graph, plus other cherry‑picked fixes.
Upgrade notes
- If upgrading from a different minor version, read the upgrade overview in the operator manual: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/
- No rollback-specific instructions are included in the release notes; consult the full changelog on GitHub for details: https://github.com/argoproj/argo-cd/compare/v3.3.4…v3.3.5
Share any feedback, issues or upgrade notes on the Argo CD GitHub so other operators can benefit from your experience.