Argo CD v3.3.8 released on 21-04-2026
Argo CD v3.3.8 is out now. Operators and teams installing or upgrading Argo CD get clarified quick-start installation steps for non‑HA and HA deployments, signed container images and provenance to verify supply-chain integrity, and a set of targeted bug fixes.
See the release notes, the GitHub release and the official operator documentation linked in the release for installation commands, verification instructions and the full changelog.
What’s in this release
- Quick Start: create the argocd namespace and apply the appropriate manifest for your deployment mode. For non‑HA use the install.yaml and for HA use ha/install.yaml; the release shows kubectl commands using –server-side –force-conflicts to install v3.3.8 (manifests hosted on raw.githubusercontent.com).
- Signed releases 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; documentation explains how to verify signatures and provenance.
- Bug fixes and changelog highlights: reverted a change that affected automatic refreshes; fixed appcontroller core-mode sync failure when server.secretkey is missing; set AppSet resource status count default to 5000; corrected CLI diffs/manifests to use DrySource revision; avoided stale informer cache in RevisionMetadata handler; reverted an autosync event message format change. Full changelog is linked in the release.
Upgrade notes
- If upgrading from a different minor version, read the official upgrading documentation before proceeding: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/
- The release notes do not include a dedicated rollback procedure; follow the upgrading documentation and your cluster’s rollback plan when testing updates.
Share your experience or report issues on the Argo CD GitHub (see the changelog and release links) or comment on the release blog post linked from the release notes.
