From e19f4b8db50360adf2d8f1daaf446fe60d8bd62c Mon Sep 17 00:00:00 2001
From: Ruben Hensen <ruben.hensen@protonmail.com>
Date: Wed, 21 Oct 2026 12:22:57 +0200
Subject: [PATCH] velero: skip the CRD upgrade hook

The hook's init container pulls docker.io/bitnami/kubectl:1.32, which
Bitnami has removed, so the sync for the new NAS address hung on
ImagePullBackOff. The chart stays at 8.4.0 and the CRDs are already in
place.
---
 velero/velero-helm.yaml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/velero/velero-helm.yaml b/velero/velero-helm.yaml
index eaf32b8..072ed8b 100644
--- a/velero/velero-helm.yaml
+++ b/velero/velero-helm.yaml
@@ -11,6 +11,11 @@ spec:
     targetRevision: 8.4.0
     helm:
       values: |
+        # 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.
+        upgradeCRDs: false
         initContainers:
           - name: velero-plugin-for-aws
             image: velero/velero-plugin-for-aws:v1.11.1