# Velero Helm values — the AUTHORITATIVE values live inline in helmrelease.yaml (this file is a
# doc pointer, kept for parity with the other components' layout).
#
# LIVE wiring (see helmrelease.yaml):
#   - provider aws + velero-plugin-for-aws (init container) → MinIO S3 http://192.168.1.9:9000
#     (path-style, bucket `velero`, region us-east-1 placeholder).
#   - deployNodeAgent:true + uploaderType:kopia → File System Backup of PVC data (no CSI data-mover).
#   - snapshotsEnabled:false → no VolumeSnapshotLocation.
#   - credentials.existingSecret: velero-cloud-credentials (SOPS `cloud` INI key, ns velero).
#   - two daily Schedules (${VELERO_BACKUP_SCHEDULE} / ttl ${VELERO_RETENTION}): the whole cluster
#     via FSB, with monitoring+unifi backed up RESOURCES-ONLY (their volume data is reconstructable).
# DR drill (tested restore) remains a Phase-4 acceptance gate (R-STATE-03) — the PM runs it post-deploy.