From bd2606591e4c47031ef98bc6d8b97b77f9d27c9d Mon Sep 17 00:00:00 2001 From: Ruben Hensen Date: Thu, 22 Oct 2026 15:32:19 +0200 Subject: [PATCH] velero: correct the upgradeCRDs comment Argo CD applies the chart's crds/ directory on every sync, so CRD updates don't depend on the hook; the 1.16 upgrade confirmed it. --- velero/velero-helm.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/velero/velero-helm.yaml b/velero/velero-helm.yaml index 097a8c1..4b804ea 100644 --- a/velero/velero-helm.yaml +++ b/velero/velero-helm.yaml @@ -17,9 +17,9 @@ spec: # cleaned up. fullnameOverride: velero # The CRD upgrade hook pulls docker.io/bitnami/kubectl, which Bitnami - # has removed, so every sync hangs on it. The CRDs only change with - # the chart version; turn this back on (with another kubectl image) - # when bumping targetRevision. + # has removed, so every sync hangs on it. Not needed anyway: Argo CD + # applies the chart's crds/ directory on every sync, which is how the + # 1.16 CRDs got in. upgradeCRDs: false initContainers: - name: velero-plugin-for-aws