# 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 v1.14.2 (init container) → the S3 endpoint
#     ${S3_BACKUP_ENDPOINT} from cluster-vars. That is a KNOB, not MinIO: dev has been running against
#     the on-Proxmox MinIO http://192.168.1.9:9000, and as of 2026-09-05 the authored target is
#     Cloudflare R2 (https://<account-id>.r2.cloudflarestorage.com) — see infra/BACKUP-R2.md.
#     Always path-style; bucket `velero`; region ${S3_BACKUP_REGION} (MinIO ignores it, R2 demands
#     exactly `auto`); per-environment prefix ${VELERO_BACKUP_PREFIX}.
#   - checksumAlgorithm: "" — REQUIRED for R2 and harmless for MinIO. The plugin defaults it to CRC32,
#     which R2 rejects with HTTP 400 InvalidArgument. Do not drop it; see helmrelease.yaml.
#   - deployNodeAgent:true + uploaderType:kopia → File System Backup of PVC data (no CSI data-mover).
#     NOTE this path uses kopia's OWN S3 client, which does not read checksumAlgorithm — backup
#     metadata and volume data are two separate S3-compatibility questions (infra/BACKUP-R2.md §7).
#   - 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.
# It is PROVEN against MinIO only; a restore from R2 has never been executed (infra/BACKUP-R2.md §5).