Skip to content

Comments

chore(deps): update dependency argoproj/argo-cd to v3.3.2#256

Merged
bkonicek merged 1 commit intomainfrom
renovate/argoproj-argo-cd-3.x
Feb 25, 2026
Merged

chore(deps): update dependency argoproj/argo-cd to v3.3.2#256
bkonicek merged 1 commit intomainfrom
renovate/argoproj-argo-cd-3.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 2, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
argoproj/argo-cd minor v3.2.6v3.3.2

Release Notes

argoproj/argo-cd (argoproj/argo-cd)

v3.3.2

Compare Source

[!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
Documentation

Full Changelog: argoproj/argo-cd@v3.3.1...v3.3.2

v3.3.1

Compare Source

[!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
Dependency updates
Other work

Full Changelog: argoproj/argo-cd@v3.3.0...v3.3.1

v3.3.0

Compare Source

[!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, like when the self-managing of Argo CD is performed with Kustomize, setting the above is not enough and there might 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.

If you hit this scenario, the remediation is to additionally set the ClientSideApplyMigration=false sync option on this Application.

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
Bug fixes

@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 463d89e to 4947728 Compare February 2, 2026 19:53
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch 2 times, most recently from 3743cc0 to eba7477 Compare February 18, 2026 14:59
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.3.0 chore(deps): update dependency argoproj/argo-cd to v3.3.1 Feb 18, 2026
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from eba7477 to e006b4e Compare February 22, 2026 17:03
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.3.1 chore(deps): update dependency argoproj/argo-cd to v3.3.2 Feb 22, 2026
@bkonicek bkonicek merged commit 1f3983f into main Feb 25, 2026
@bkonicek bkonicek deleted the renovate/argoproj-argo-cd-3.x branch February 25, 2026 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant