Skip to content

Releases: argoproj/argo-cd

v3.1.13

Choose a tag to compare

@github-actions github-actions released this 25 Mar 15:04
ed35bc3

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.1.13/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.1.13/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes

Dependency updates

Other work

  • 12c8d42: chore: use base ref for cherry-pick prs (cherry-pick #26551 for 3.1) (#26555) (@argo-cd-cherry-pick-bot[bot])

Full Changelog: v3.1.12...v3.1.13

v3.4.0-rc2

v3.4.0-rc2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Mar 23:50
9044c6c

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.4.0-rc2/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.4.0-rc2/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Features

  • 3157fb1: feat(helm): support wildcard glob patterns for valueFiles (cherry-pick #26768 for 3.4) (#26919) (@argo-cd-cherry-pick-bot[bot])

Bug fixes

  • 21e13a6: fix(UI): show RollingSync step clearly when labels match no step (cherry-pick #26877 for 3.4) (#26882) (@argo-cd-cherry-pick-bot[bot])
  • e70034a: fix(ci): add .gitkeep to images dir (cherry-pick #26892 for 3.4) (#26912) (@argo-cd-cherry-pick-bot[bot])
  • 5deef68: fix(ui): include _-prefixed dirs in embedded assets (cherry-pick #26589 for 3.4) (#26909) (@argo-cd-cherry-pick-bot[bot])
  • 226178c: fix: stack overflow when processing circular ownerrefs in resource graph (#26783) (cherry-pick #26790 for 3.4) (#26878) (@argo-cd-cherry-pick-bot[bot])

Full Changelog: v3.4.0-rc1...v3.4.0-rc2

v3.4.0-rc1

v3.4.0-rc1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Mar 11:34
d91a2ab

Important

Following Helm 3.19.0 change in how Helm interprets K8s cluster version, this Argo CD release contains a change that aligns how Argo CD interprets K8s cluster version with Helm behavior.

Impact: Application Sets with Cluster Generators, that fetch clusters based on their Kubernetes version and use argocd.argoproj.io/auto-label-cluster-info on the cluster secret, need to be updated to use argocd.argoproj.io/kubernetes-version with the vMajor.Minor.Patch format instead of the previous Major.Minor format.

More details here: https://argo-cd.readthedocs.io/en/release-3.4/operator-manual/upgrading/3.3-3.4/#cluster-version-format-change

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.4.0-rc1/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.4.0-rc1/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Features

Bug fixes

Read more

v3.3.4

Choose a tag to compare

@github-actions github-actions released this 16 Mar 11:44
34ccdfc

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.4/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.4/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes

  • 182e4c6: fix(ci): Add missing git-lfs installer checksum for ppc64le (cherry-pick #26835 for 3.3) (#26836) (@argo-cd-cherry-pick-bot[bot])
  • 2fcc40a: fix: skip token refresh threshold parsing in unrelated components (cherry-pick 3.3) (#26806) (@gdsoumya)

Documentation

  • 01b86e7: docs: clarify cluster version change impact for ClusterGenerator, CMP Plugins and migration (#26851) (@reggie-k)

Other work

Full Changelog: v3.3.3...v3.3.4

v3.3.3

Choose a tag to compare

@github-actions github-actions released this 09 Mar 16:14
ff239dc

Important

Following Helm 3.19.0 change in how Helm interprets K8s cluster version, Argo CD 3.3.3 release contains a change that aligns how Argo CD interprets K8s cluster version with Helm behavior.

Impact: Application Sets with Cluster Generators, that fetch clusters based on their Kubernetes version and use argocd.argoproj.io/auto-label-cluster-info on the cluster secret, need to be updated to use argocd.argoproj.io/kubernetes-version with the vMajor.Minor.Patch format instead of the previous Major.Minor format.

More details here: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#cluster-version-format-change

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.3/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.3/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes

  • 6224d67: fix(actions): Use correct annotation for CNPG suspend/resume (cherry-pick #26711 for 3.3) (#26727) (@argo-cd-cherry-pick-bot[bot])
  • 968c633: fix(controller): handle comma-separated hook annotations for PreDelete/PostDelete hooks (cherry-pick #26420 for 3.3) (#26586) (@argo-cd-cherry-pick-bot[bot])
  • 4411801: fix(health): use note.drySha when available (cherry-pick #26698 for 3.3) (#26750) (@argo-cd-cherry-pick-bot[bot])
  • 3d3760f: fix(ui): standard resource icons are not displayed properly.#26216 (cherry-pick #26228 for 3.3) (#26380) (@argo-cd-cherry-pick-bot[bot])
  • c6df35d: fix: consistency of kubeversion with helm version 3 3 (#26744) (@ppapapetrou76)
  • 5e19021: fix: multi-level cross-namespace hierarchy traversal for cluster-scop… (#26640) (@agaudreault)

Other work

  • c61c593: chore: use base ref for cherry-pick prs (cherry-pick #26551 for 3.3) (#26553) (@argo-cd-cherry-pick-bot[bot])

Full Changelog: v3.3.2...v3.3.3

v3.3.2

Choose a tag to compare

@github-actions github-actions released this 22 Feb 13:18
8a3940d

Important

Before upgrading all types of Argo CD installations to this release, please read the upgrade guide first:
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

Upgrading Argo CD which is managing itself

Users who have an Argo CD Application that manages their Argo CD installation, must enable ServerSideApply=true sync option on this Application in order for the upgrade to succeed.

The issue with failed to perform client-side apply migration that existed on version 3.3.0 and 3.3.1 has been solved in this release: #26279

For users who have previously upgraded to Argo CD 3.3.0or 3.3.1 and applied the temporary remediation of ClientSideApplyMigration=false sync option on the Application that manages their Argo CD, are required to remove this setting to restore the default behavior of performing the migration.
The reason for removing the ClientSideApplyMigration=false sync option is that it may cause conflicts between Argo CD K8s field manager and other field managers at a later point in time.

More details here:
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.2/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.2/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes

  • 67c2319: fix: use csapgrade to patch managedFields for client-side apply migration (cherry-pick #26289 for 3.3) (#26516) (@argo-cd-cherry-pick-bot[bot])

Documentation

  • 1bf62ae: docs: instruct to enable ClientSideApplyMigration in 3.3.2 (cherry-pick #26547 for 3.3) (#26549) (@argo-cd-cherry-pick-bot[bot])

Full Changelog: v3.3.1...v3.3.2

v3.3.1

Choose a tag to compare

@github-actions github-actions released this 18 Feb 12:30
326a1db

Important

Before upgrading all types of Argo CD installations to this release, please read the upgrade guide first:
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

Upgrading Argo CD which is managing itself

Users who have an Argo CD Application that manages their Argo CD installation, must enable ServerSideApply=true sync option on this Application in order for the upgrade to succeed.

In some cases, there may be a sync error like Failed to perform client-side apply migration: failed to perform client-side apply migration on manager kubectl-client-side-apply.

We are currently working on a long-term fix to this issue, the progress can be tracked here: #26279

A temporary remediation is to additionally set the ClientSideApplyMigration=false sync option on this Application. This solution is temporary and not recommended for the long run because it may result in conflicts between Argo CD K8s field manager and other field managers at a later point in time, and if you use it, you will need to remove it after the above issue is fixed.

More details here:
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.1/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.1/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes

  • 8449d9a: fix(server): OIDC config via secrets fails (#18269) (cherry-pick #26214 for 3.3) (#26423) (@argo-cd-cherry-pick-bot[bot])
  • d0b2a6c: fix: Fix excessive ls-remote requests on monorepos with Auto Sync enabled apps (26277) (cherry-pick #26278 for 3.3) (#26372) (@argo-cd-cherry-pick-bot[bot])
  • e464f6a: fix: AppProject finalizer should consider apps in all allowed namespaces (#24347) (cherry-pick #26416 for 3.3) (#26480) (@argo-cd-cherry-pick-bot[bot])
  • 445916f: fix: compressedLayerExtracterStore+isCompressedLayer - allow tar.gzip suffixes (cherry-pick #26355 for 3.3) (#26376) (@argo-cd-cherry-pick-bot[bot])

Dependency updates

  • 6126798: chore(deps): Upgrade Kustomize to 5.8.1 (cherry-pick #26367 for 3.3) (#26369) (@argo-cd-cherry-pick-bot[bot])

Other work

  • 92df21c: chore(appset): cherry-pick basic progressive sync e2e tests (#26092) (#26191) (@ranakan19)
  • 4b0a2c0: chore: bumps ubuntu base docker image to 25.10 (cherry-pick #25758 for 3.3) (#26436) (@argo-cd-cherry-pick-bot[bot])
  • 273683b: chore: placate Sonar by ignoring testdata files (cherry-pick #26371 for 3.3) (#26377) (@argo-cd-cherry-pick-bot[bot])
  • 8df5e96: test(e2e): CMP test fails locally on Mac (cherry-pick #25901 for 3.3) (#26340) (@argo-cd-cherry-pick-bot[bot])
  • 2449314: test(e2e): add isolation by ensuring unique name (cherry-pick #25724 for 3.3) (#26287) (@ranakan19)
  • c4f0cd3: test(e2e): configurable tmp dir locally (#25780) (#26339) (@ranakan19)
  • 55d0d09: test(e2e): fix TestDeletionConfirmation flakiness (cherry-pick #25902 for 3.3) (#26284) (@argo-cd-cherry-pick-bot[bot])
  • 6f270cc: test(e2e): oras binary not found locally if not installed in path (cherry-pick #25751 for 3.3) (#26337) (@argo-cd-cherry-pick-bot[bot])
  • 54f2916: test(e2e): unstable CMP e2e test when running locally (cherry-pick #25752 for 3.3) (#26288) (@argo-cd-cherry-pick-bot[bot])
  • 0038fce: test(e2e): update local certs so they are valid on MacOS (cherry-pick #25864 for 3.3) (#26338) (@argo-cd-cherry-pick-bot[bot])

Full Changelog: v3.3.0...v3.3.1

v3.2.7

Choose a tag to compare

@github-actions github-actions released this 18 Feb 13:45
48549a2

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.2.7/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.2.7/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes

  • ca08f90: fix(server): OIDC config via secrets fails (#18269) (cherry-pick #26214 for 3.2) (#26389) (@argo-cd-cherry-pick-bot[bot])
  • 10c3fd0: fix: Fix excessive ls-remote requests on monorepos with Auto Sync enabled apps (26277) (cherry-pick #26278 for 3.2) (#26502) (@dudinea)
  • 9c128e2: fix: compressedLayerExtracterStore+isCompressedLayer - allow tar.gzip suffixes (cherry-pick #26355 for 3.2) (#26375) (@argo-cd-cherry-pick-bot[bot])

Dependency updates

Other work

  • 1f03b27: ci: exclude testdata from sonar.exclusions (cherry-pick #26398 and #26371 for 3.2) (#26424) (@argo-cd-cherry-pick-bot[bot])

Full Changelog: v3.2.6...v3.2.7

v3.3.0

Choose a tag to compare

@github-actions github-actions released this 02 Feb 08:13
fd6b7d5

Important

Before upgrading all types of Argo CD installations to this release, please read the upgrade guide first:
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

Upgrading Argo CD which is managing itself

Users who have an Argo CD Application that manages their Argo CD installation, must enable ServerSideApply=true sync option on this Application in order for the upgrade to succeed.

In some cases, there may be a sync error like Failed to perform client-side apply migration: failed to perform client-side apply migration on manager kubectl-client-side-apply.

We are currently working on a long-term fix to this issue, the progress can be tracked here: #26279

A temporary remediation is to additionally set the ClientSideApplyMigration=false sync option on this Application. This solution is temporary and not recommended for the long run because it may result in conflicts between Argo CD K8s field manager and other field managers at a later point in time, and if you use it, you will need to remove it after the above issue is fixed.

More details here:
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.0/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.0/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post.

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Features

Read more

v3.3.0-rc4

v3.3.0-rc4 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 22 Jan 20:23
436da4e

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.0-rc4/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.0-rc4/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes

  • 15568cb: fix(appset): do not trigger reconciliation on appsets not part of allowed namespaces when updating a cluster secret (cherry-pick #25622 for 3.3) (#25909) (@argo-cd-cherry-pick-bot[bot])
  • b52a075: fix(hydrator): .gitattributes include deeply nested files (#25870) (cherry-pick #26011 for 3.3) (#26013) (@argo-cd-cherry-pick-bot[bot])
  • 48a9dcc: fix(hydrator): empty links for failed operation (#25025) (cherry-pick #26014 for 3.3) (#26018) (@argo-cd-cherry-pick-bot[bot])
  • 0fa47b1: fix(hydrator): pass destination.namespace to manifest rendering (#25478) (cherry-pick #25699 for 3.3) (#26019) (@argo-cd-cherry-pick-bot[bot])
  • 32c32a6: fix: Only show please update resource specification message when spec… (cherry-pick #25066 for 3.3) (#25894) (@argo-cd-cherry-pick-bot[bot])
  • 74de77a: fix: Toggle automated.enabled to disable auto-sync for rollbacks (cherry-pick #25719 for 3.3) (#25943) (@argo-cd-cherry-pick-bot[bot])
  • a6472c8: fix: allow docker dhi helm charts to be used (cherry-pick #25835 for 3.3) (#25964) (@argo-cd-cherry-pick-bot[bot])
  • cd6a9aa: fix: cherry pick #25516 to release-3.3 (#26114) (@FourFifthsCode)
  • 8fbb44c: fix: close response body on error paths to prevent connection leak (cherry-pick #25824 for 3.3) (#26005) (@argo-cd-cherry-pick-bot[bot])
  • 3d64c21: fix: invalid error message on health check failure (#26040) (cherry-pick #26039 for 3.3) (#26063) (@argo-cd-cherry-pick-bot[bot])
  • 28e8472: fix: nil and empty ignoredifferences (cherry-pick #25980 for 3.3) (#26000) (@argo-cd-cherry-pick-bot[bot])

Documentation

Dependency updates

Other work

  • 675f8cf: chore(cherry-pick-3.3): bump expr to v1.17.7 (#25888) (@nitishfy)
  • efca5b9: chore: bumps golang version everywhere to the latest 1.25.5 (cherry-pick #25716 for 3.3) (#25808) (@argo-cd-cherry-pick-bot[bot])
  • 9ae26e4: ci: test against k8s 1.34.2 (cherry-pick #25856 for 3.3) (#25858) (@argo-cd-cherry-pick-bot[bot])

Full Changelog: v3.3.0-rc3...v3.3.0-rc4