From ff73f99d438e420e3a185be80ca97f5f17521321 Mon Sep 17 00:00:00 2001 From: Ruben Hensen Date: Thu, 22 Oct 2026 09:23:51 +0200 Subject: [PATCH] velero: name the release resources "velero" so repo maintenance runs Velero 1.15 builds kopia repository maintenance jobs from a Deployment called "velero" in its namespace. Ours was velero-helm, so every BackupRepository reported 'error to build maintenance job: Deployment.apps "velero" not found' and the repos on the NAS were never cleaned up, some not since March 2025. fullnameOverride renames the Deployment, Service, ServiceAccount and RBAC; the old velero-helm objects get deleted by hand since this app doesn't prune. --- velero/velero-helm.yaml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/velero/velero-helm.yaml b/velero/velero-helm.yaml index abe86ff..0ea5469 100644 --- a/velero/velero-helm.yaml +++ b/velero/velero-helm.yaml @@ -11,6 +11,11 @@ spec: targetRevision: 8.4.0 helm: values: | + # Velero builds its repository maintenance jobs from a Deployment + # named "velero". Under the default name (velero-helm) every + # 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. The CRDs only change with # the chart version; turn this back on (with another kubectl image)