From dfdc4451fbc9f949b10afc2683ea296ad8235b22 Mon Sep 17 00:00:00 2001
From: Ruben Hensen <ruben.hensen@protonmail.com>
Date: Wed, 21 Oct 2026 12:33:31 +0200
Subject: [PATCH] velero: raise the server memory limit to 2Gi

At 512Mi the server has been OOMKilled 314 times. With the bucket
reachable again it died 23 seconds into a manual backup of ~14.7k items,
which then got marked Failed on restart. opti1 has 32GB.
---
 velero/velero-helm.yaml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/velero/velero-helm.yaml b/velero/velero-helm.yaml
index 072ed8b..da874e9 100644
--- a/velero/velero-helm.yaml
+++ b/velero/velero-helm.yaml
@@ -48,13 +48,15 @@ spec:
         nodeAgent:
           containerSecurityContext:
             privileged: true
+        # 512Mi got the server OOMKilled 314 times, including halfway
+        # through a backup of ~14.7k items.
         resources:
           requests:
             cpu: 100m
-            memory: 256Mi
+            memory: 512Mi
           limits:
             cpu: 500m
-            memory: 512Mi
+            memory: 2Gi
         
   destination:
     server: https://kubernetes.default.svc