Skip to content

chore(deps): update quay.io/argoproj/argocd docker tag to v3.3.0#271

Open
vshn-renovate wants to merge 1 commit intomasterfrom
commodore-renovate/quay.io-argoproj-argocd-3.x
Open

chore(deps): update quay.io/argoproj/argocd docker tag to v3.3.0#271
vshn-renovate wants to merge 1 commit intomasterfrom
commodore-renovate/quay.io-argoproj-argocd-3.x

Conversation

@vshn-renovate
Copy link
Contributor

@vshn-renovate vshn-renovate commented Feb 2, 2026

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
quay.io/argoproj/argocd minor v3.2.6v3.3.0

Release Notes

argoproj/argo-cd (quay.io/argoproj/argocd)

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@vshn-renovate vshn-renovate changed the title chore(deps): update quay.io/argoproj/argocd docker tag to v3.3.0 chore(deps): update quay.io/argoproj/argocd docker tag to v3.3.0 - autoclosed Feb 6, 2026
@vshn-renovate vshn-renovate deleted the commodore-renovate/quay.io-argoproj-argocd-3.x branch February 6, 2026 09:07
Signed-off-by: Renovate Bot <tech+renovate@vshn.ch>
@vshn-renovate vshn-renovate changed the title chore(deps): update quay.io/argoproj/argocd docker tag to v3.3.0 - autoclosed chore(deps): update quay.io/argoproj/argocd docker tag to v3.3.0 Feb 6, 2026
@vshn-renovate vshn-renovate reopened this Feb 6, 2026
@vshn-renovate vshn-renovate force-pushed the commodore-renovate/quay.io-argoproj-argocd-3.x branch 2 times, most recently from 7b271c3 to 201ee93 Compare February 6, 2026 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant