From 1926ccc42ad831e689167bfbe0aa293a7cc492c4 Mon Sep 17 00:00:00 2001
From: Ruben Hensen <ruben.hensen@protonmail.com>
Date: Fri, 23 Oct 2026 22:47:27 +0200
Subject: [PATCH] velero: upgrade to 1.18.2 (chart 12.2.1)

No breaking changes for this setup: the chart renders the same resources and server flags, and chart 12 only dropped the Bitnami kubectl image from the CRD hook, which stays off because Argo CD applies the CRDs. The AWS plugin goes to v1.14.4, the line for Velero 1.18.
---
 velero/velero-helm.yaml | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/velero/velero-helm.yaml b/velero/velero-helm.yaml
index 703e1e8..89d8aa7 100644
--- a/velero/velero-helm.yaml
+++ b/velero/velero-helm.yaml
@@ -8,7 +8,7 @@ spec:
   source:
     chart: velero
     repoURL: https://vmware-tanzu.github.io/helm-charts
-    targetRevision: 11.4.0
+    targetRevision: 12.2.1
     helm:
       values: |
         # Velero builds its repository maintenance jobs from a Deployment
@@ -16,14 +16,13 @@ spec:
         # maintenance run failed and the kopia repos on the NAS were never
         # cleaned up.
         fullnameOverride: velero
-        # The CRD upgrade hook pulls docker.io/bitnami/kubectl, which Bitnami
-        # 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.
+        # No CRD upgrade hook: Argo CD applies the chart's crds/ directory on
+        # every sync. (Before chart 12 the hook also pulled
+        # docker.io/bitnami/kubectl, which Bitnami removed, and hung.)
         upgradeCRDs: false
         initContainers:
           - name: velero-plugin-for-aws
-            image: velero/velero-plugin-for-aws:v1.13.2
+            image: velero/velero-plugin-for-aws:v1.14.4
             volumeMounts:
               - mountPath: /target
                 name: plugins