Velero

Velero can back up resources deployed by this chart without any chart-level configuration. The simplest setup is to configure Velero at the server level to automatically snapshot all PVCs in the namespace — no annotations or chart changes needed.

For file-system level backup (Restic/Kopia) or when you need per-pod control, Velero uses pod annotations to determine which volumes to back up:

podAnnotations:
  backup.velero.io/backup-volumes: data,config        # include these volumes
  backup.velero.io/backup-volumes-excludes: cache     # or exclude specific volumes

The volume names must match the names in your persistence: configuration. For example, if you have persistence.data: and persistence.config:, annotate with data,config.

backups: named schedules

A future version of this chart will support generating Velero Schedule CRs directly, following the same pattern as cronJobs::

backups:
  daily:                      # bare key uses all defaults (@daily, 30-day retention)
  weekly:
    schedule: "@weekly"
    ttl: 2160h
    storageLocation: offsite

See the Roadmap for details.