Skip to content

Comments

argocd: update quay.io/argoproj/argocd Docker tag to v3.3.2#387

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/quay.io-argoproj-argocd-3.x
Open

argocd: update quay.io/argoproj/argocd Docker tag to v3.3.2#387
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/quay.io-argoproj-argocd-3.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 18, 2026

This PR contains the following updates:

Package Type Update Change
quay.io/argoproj/argocd Kustomization patch v3.3.0v3.3.2

Release Notes

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

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


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 was generated by Mend Renovate. View the repository job log.

@github-actions
Copy link

github-actions bot commented Feb 18, 2026

Infro diff for 6879984

argocd.hashbang.sh > argocd (0 files changed)

Details
time="2026-02-22T17:14:32Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."
time="2026-02-22T17:14:47Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."

===== apps/Deployment argocd/argocd-applicationset-controller ======
--- /tmp/argocd-diff3714874431/argocd-applicationset-controller-live.yaml
+++ /tmp/argocd-diff3714874431/argocd-applicationset-controller
@@ -579,7 +579,7 @@
               key: applicationsetcontroller.status.max.resources.count
               name: argocd-cmd-params-cm
               optional: true
-        image: quay.io/argoproj/argocd:v3.3.0@sha256:ed0740273790e58154816104c1e1b41fb308a9c516ade3d0f195fa56f1840cca
+        image: quay.io/argoproj/argocd:v3.3.2@sha256:5882f28f7aaeaac397949c4511fdc1ad66c1260af44166ccf7e57aca3d7b9797
         imagePullPolicy: Always
         name: argocd-applicationset-controller
         ports:

===== apps/Deployment argocd/argocd-dex-server ======
--- /tmp/argocd-diff621887658/argocd-dex-server-live.yaml
+++ /tmp/argocd-diff621887658/argocd-dex-server
@@ -358,7 +358,7 @@
         - -n
         - /usr/local/bin/argocd
         - /shared/argocd-dex
-        image: quay.io/argoproj/argocd:v3.3.0@sha256:ed0740273790e58154816104c1e1b41fb308a9c516ade3d0f195fa56f1840cca
+        image: quay.io/argoproj/argocd:v3.3.2@sha256:5882f28f7aaeaac397949c4511fdc1ad66c1260af44166ccf7e57aca3d7b9797
         imagePullPolicy: Always
         name: copyutil
         resources: {}

===== apps/Deployment argocd/argocd-notifications-controller ======
--- /tmp/argocd-diff533064692/argocd-notifications-controller-live.yaml
+++ /tmp/argocd-diff533064692/argocd-notifications-controller
@@ -276,7 +276,7 @@
               key: notificationscontroller.repo.server.plaintext
               name: argocd-cmd-params-cm
               optional: true
-        image: quay.io/argoproj/argocd:v3.3.0@sha256:ed0740273790e58154816104c1e1b41fb308a9c516ade3d0f195fa56f1840cca
+        image: quay.io/argoproj/argocd:v3.3.2@sha256:5882f28f7aaeaac397949c4511fdc1ad66c1260af44166ccf7e57aca3d7b9797
         imagePullPolicy: Always
         livenessProbe:
           failureThreshold: 3

===== apps/Deployment argocd/argocd-redis ======
--- /tmp/argocd-diff2135365843/argocd-redis-live.yaml
+++ /tmp/argocd-diff2135365843/argocd-redis
@@ -260,7 +260,7 @@
         - argocd
         - admin
         - redis-initial-password
-        image: quay.io/argoproj/argocd:v3.3.0@sha256:ed0740273790e58154816104c1e1b41fb308a9c516ade3d0f195fa56f1840cca
+        image: quay.io/argoproj/argocd:v3.3.2@sha256:5882f28f7aaeaac397949c4511fdc1ad66c1260af44166ccf7e57aca3d7b9797
         imagePullPolicy: IfNotPresent
         name: secret-init
         resources: {}

===== apps/Deployment argocd/argocd-repo-server ======
--- /tmp/argocd-diff3778547478/argocd-repo-server-live.yaml
+++ /tmp/argocd-diff3778547478/argocd-repo-server
@@ -919,7 +919,7 @@
           value: /helm-working-dir
         - name: HELM_DATA_HOME
           value: /helm-working-dir
-        image: quay.io/argoproj/argocd:v3.3.0@sha256:ed0740273790e58154816104c1e1b41fb308a9c516ade3d0f195fa56f1840cca
+        image: quay.io/argoproj/argocd:v3.3.2@sha256:5882f28f7aaeaac397949c4511fdc1ad66c1260af44166ccf7e57aca3d7b9797
         imagePullPolicy: Always
         livenessProbe:
           failureThreshold: 3
@@ -992,7 +992,7 @@
         env:
         - name: GNUPGHOME
           value: /gnupg-home/.gnupg
-        image: quay.io/argoproj/argocd:v3.3.0@sha256:ed0740273790e58154816104c1e1b41fb308a9c516ade3d0f195fa56f1840cca
+        image: quay.io/argoproj/argocd:v3.3.2@sha256:5882f28f7aaeaac397949c4511fdc1ad66c1260af44166ccf7e57aca3d7b9797
         imagePullPolicy: IfNotPresent
         name: import-gpg-key
         resources: {}
@@ -1024,7 +1024,7 @@
         command:
         - sh
         - -c
-        image: quay.io/argoproj/argocd:v3.3.0@sha256:ed0740273790e58154816104c1e1b41fb308a9c516ade3d0f195fa56f1840cca
+        image: quay.io/argoproj/argocd:v3.3.2@sha256:5882f28f7aaeaac397949c4511fdc1ad66c1260af44166ccf7e57aca3d7b9797
         imagePullPolicy: IfNotPresent
         name: copyutil
         resources: {}

===== apps/Deployment argocd/argocd-server ======
--- /tmp/argocd-diff1221803360/argocd-server-live.yaml
+++ /tmp/argocd-diff1221803360/argocd-server
@@ -903,7 +903,7 @@
               key: server.sync.replace.allowed
               name: argocd-cmd-params-cm
               optional: true
-        image: quay.io/argoproj/argocd:v3.3.0@sha256:ed0740273790e58154816104c1e1b41fb308a9c516ade3d0f195fa56f1840cca
+        image: quay.io/argoproj/argocd:v3.3.2@sha256:5882f28f7aaeaac397949c4511fdc1ad66c1260af44166ccf7e57aca3d7b9797
         imagePullPolicy: Always
         livenessProbe:
           failureThreshold: 3

===== apps/StatefulSet argocd/argocd-application-controller ======
--- /tmp/argocd-diff2394799855/argocd-application-controller-live.yaml
+++ /tmp/argocd-diff2394799855/argocd-application-controller
@@ -768,7 +768,7 @@
               optional: true
         - name: KUBECACHEDIR
           value: /tmp/kubecache
-        image: quay.io/argoproj/argocd:v3.3.0@sha256:ed0740273790e58154816104c1e1b41fb308a9c516ade3d0f195fa56f1840cca
+        image: quay.io/argoproj/argocd:v3.3.2@sha256:5882f28f7aaeaac397949c4511fdc1ad66c1260af44166ccf7e57aca3d7b9797
         imagePullPolicy: Always
         name: argocd-application-controller
         ports:

argocd.hashbang.sh > cloudnative-pg (0 files changed)

Details
time="2026-02-22T17:15:06Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."
time="2026-02-22T17:15:16Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."

===== coordination.k8s.io/Lease /db9c8771.cnpg.io ======
--- /tmp/argocd-diff3657625687/db9c8771.cnpg.io-live.yaml
+++ /tmp/argocd-diff3657625687/db9c8771.cnpg.io
@@ -0,0 +1,11 @@
+apiVersion: coordination.k8s.io/v1
+kind: Lease
+metadata:
+  annotations:
+    argocd.argoproj.io/tracking-id: cloudnative-pg:coordination.k8s.io/Lease:cloudnative-pg/db9c8771.cnpg.io
+  labels:
+    app.kubernetes.io/component: manager
+    app.kubernetes.io/instance: cloudnative-pg
+    app.kubernetes.io/name: cloudnative-pg
+  name: db9c8771.cnpg.io
+spec: {}

argocd.hashbang.sh > external-dns (0 files changed)

Details
time="2026-02-22T17:15:18Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."
time="2026-02-22T17:15:22Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."

===== apps/Deployment external-dns/external-dns ======
--- /tmp/argocd-diff1394627986/external-dns-live.yaml
+++ /tmp/argocd-diff1394627986/external-dns
@@ -8,6 +8,7 @@
       {"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"labels":{"app.kubernetes.io/name":"external-dns"},"name":"external-dns","namespace":"external-dns"},"spec":{"selector":{"matchLabels":{"app.kubernetes.io/name":"external-dns"}},"strategy":{"type":"Recreate"},"template":{"metadata":{"labels":{"app.kubernetes.io/name":"external-dns"}},"spec":{"containers":[{"args":["--source=service","--source=ingress","--registry=txt","--provider=aws","--txt-owner-id=digitalocean-hashbang","--txt-prefix=_owner.","--source=crd","--domain-filter=hashbang.sh","--managed-record-types=A","--managed-record-types=CNAME","--managed-record-types=TXT"],"env":[{"name":"AWS_REGION","value":"us-west-2"},{"name":"AWS_ACCESS_KEY_ID","value":"AKIAR7CEWFK35SZX5S66"},{"name":"AWS_SECRET_ACCESS_KEY","valueFrom":{"secretKeyRef":{"key":"key","name":"external-dns-iam"}}}],"image":"registry.k8s.io/external-dns/external-dns:v0.20.0@sha256:ddc7f4212ed09a21024deb1f470a05240837712e74e4b9f6d1f2632ff10672e7","name":"external-dns","ports":[{"containerPort":7979,"name":"metrics"}]}],"securityContext":{"fsGroup":65534},"serviceAccountName":"external-dns"}}}}
   generation: 12
   labels:
+    app.kubernetes.io/instance: external-dns
     app.kubernetes.io/name: external-dns
   managedFields:
   - apiVersion: apps/v1
@@ -162,11 +163,6 @@
         - --provider=aws
         - --txt-owner-id=digitalocean-hashbang
         - --txt-prefix=_owner.
-        - --source=crd
-        - --domain-filter=hashbang.sh
-        - --managed-record-types=A
-        - --managed-record-types=CNAME
-        - --managed-record-types=TXT
         env:
         - name: AWS_REGION
           value: us-west-2

@renovate renovate bot changed the title argocd: update quay.io/argoproj/argocd Docker tag to v3.3.1 argocd: update quay.io/argoproj/argocd Docker tag to v3.3.1 - autoclosed Feb 18, 2026
@renovate renovate bot closed this Feb 18, 2026
@renovate renovate bot deleted the renovate/quay.io-argoproj-argocd-3.x branch February 18, 2026 21:04
@renovate renovate bot changed the title argocd: update quay.io/argoproj/argocd Docker tag to v3.3.1 - autoclosed argocd: update quay.io/argoproj/argocd Docker tag to v3.3.1 Feb 19, 2026
@renovate renovate bot reopened this Feb 19, 2026
@renovate renovate bot force-pushed the renovate/quay.io-argoproj-argocd-3.x branch 2 times, most recently from 985bf1a to 8eccdb7 Compare February 19, 2026 01:42
@renovate renovate bot changed the title argocd: update quay.io/argoproj/argocd Docker tag to v3.3.1 argocd: update quay.io/argoproj/argocd Docker tag to v3.3.2 Feb 22, 2026
@renovate renovate bot force-pushed the renovate/quay.io-argoproj-argocd-3.x branch from 8eccdb7 to 899813e Compare February 22, 2026 17:14
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.

0 participants