From ce1115d4f9d80cf41d1a1691dbd5e6d298470e82 Mon Sep 17 00:00:00 2001
From: Ruben Hensen <ruben.hensen@protonmail.com>
Date: Thu, 22 Oct 2026 15:30:11 +0200
Subject: [PATCH] velero: upgrade to 1.16.2 (chart 10.1.3)

Velero 1.15 is only tested up to Kubernetes 1.31; 1.16 is tested on 1.33.
The AWS plugin moves along to v1.12.2. Argo CD applies the chart's crds/
directory itself, so the CRD schema update doesn't need the disabled
upgrade hook. No backup was running.
---
 velero/velero-helm.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/velero/velero-helm.yaml b/velero/velero-helm.yaml
index 0ea5469..097a8c1 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: 8.4.0
+    targetRevision: 10.1.3
     helm:
       values: |
         # Velero builds its repository maintenance jobs from a Deployment
@@ -23,7 +23,7 @@ spec:
         upgradeCRDs: false
         initContainers:
           - name: velero-plugin-for-aws
-            image: velero/velero-plugin-for-aws:v1.11.1
+            image: velero/velero-plugin-for-aws:v1.12.2
             volumeMounts:
               - mountPath: /target
                 name: plugins