Skip to content

Commit 1313b01

Browse files
committed
feat(backup-exporter): allow reading velero volume policies
The velero chart renders a resource policy ConfigMap from skipVolumePolicies, telling Velero to skip volumes backed up logically instead. backup-exporter reads it so those volumes are not reported as missing backups; without the rule it fails safe but silently, alerting on every skipped volume forever.
1 parent 2d2a253 commit 1313b01

2 files changed

Lines changed: 11 additions & 1 deletion

File tree

argocd-helm-charts/backup-exporter/Chart.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,5 +2,5 @@ apiVersion: v2
22
name: backup-exporter
33
description: A Helm chart for the Obmondo Backup Exporter — reports PostgreSQL (CNPG logical and WAL), Velero, MongoDB and Sealed Secrets backup health by reading object storage directly, as Prometheus metrics and a JSON API.
44
type: application
5-
version: 0.3.3
5+
version: 0.3.4
66
appVersion: "v1.2.1"

argocd-helm-charts/backup-exporter/templates/clusterrole.yaml

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,16 @@ rules:
4747
resources: ["deployments"]
4848
verbs: ["get", "list"]
4949

50+
# Velero volume policies. A Schedule can name a ConfigMap that tells Velero to
51+
# skip a volume outright -- the velero chart renders exactly that from
52+
# skipVolumePolicies, for databases backed up logically instead. The exporter
53+
# reads it so those volumes are not reported as missing backups. Removing this
54+
# rule fails safe but silently: the policy cannot be read, so every skipped
55+
# volume alerts as unbacked, once per volume, forever.
56+
- apiGroups: [""]
57+
resources: ["configmaps"]
58+
verbs: ["get"]
59+
5060
# Namespaces for cross-namespace discovery
5161
- apiGroups: [""]
5262
resources: ["namespaces"]

0 commit comments

Comments
 (0)