Argo CD v3.4.1 released on 06-05-2026
Argo CD v3.4.1 is out now. Operators and ApplicationSet users should note a compatibility change: Argo CD’s Kubernetes version interpretation has been aligned with Helm 3.19.x, which affects auto‑labelling and cluster selectors.
Check the project GitHub for install manifests (non‑HA and HA) and the Argo CD documentation for upgrade notes and signature verification: manifests are available at the v3.4.1 tag on raw.githubusercontent.com and the upgrade/verification docs on argo-cd.readthedocs.io.
What’s in this release
- Cluster version format change: the auto‑label key argocd.argoproj.io/auto-label-cluster-info is replaced by argocd.argoproj.io/kubernetes-version; values must use the vMajor.Minor.Patch format (for example v1.28.2) to match Helm 3.19.x behaviour.
- ApplicationSet and UI improvements: Health field in ApplicationSet status, listResourceEvents and watch APIs, AppSet tree‑view/details and list/filter pages, AppSet slide‑out summary, post‑generator selector fixes and performance optimisations when reading cluster secrets.
- Helm and repository updates: support for wildcard glob patterns in valueFiles, custom User‑Agent headers for Helm repo requests, and dependency/security bumps including Helm 3.19.4.
Upgrade notes
- Breaking change for Cluster Generator users: update any ApplicationSets that rely on auto‑labeled cluster versions to use argocd.argoproj.io/kubernetes-version with vMajor.Minor.Patch values. See the 3.3→3.4 upgrade notes for migration guidance: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.3-3.4/#cluster-version-format-change
- If you need the install manifests, use the v3.4.1 manifests on GitHub (non‑HA and HA examples) at the raw.githubusercontent.com URLs for the v3.4.1 tag; verify signed images and provenance as documented before rolling out or reverting.
Share your experience with the upgrade or any migration issues on the Argo CD GitHub so others can benefit from real‑world notes.
