home-network-k3s-impl/platform/velero

platform/velero

Velero — off-cluster backup and DR of Kubernetes resource state + PVC data.

• Governing ADR: ADR-0003 — Longhorn (+ bulk tier + Velero)
• Spec: docs/04 — Storage & State
• Serves: R-STATE-03
• Owner: WS-STORAGE

What this is (LIVE)

Flux HelmRelease (Velero chart 8.x / Velero 1.15.x) wired to the on-Proxmox MinIO S3 target:

• Endpoint: http://192.168.1.9:9000 (plain HTTP, path-style, region us-east-1 placeholder)
• BucketStorageLocation default: provider aws, bucket velero, s3ForcePathStyle=true.
• AWS plugin (velero/velero-plugin-for-aws) loaded as an init container.
• File System Backup (kopia): deployNodeAgent=true, uploaderType=kopia, snapshotsEnabled=false — storage-agnostic PVC backup, no CSI snapshot / data-mover.
• Credentials: velero-cloud-credentials — a SOPS Secret (velero-cloud.sops.yaml) holding the cloud INI key, the scoped MinIO key limited to the velero+cnpg buckets. Kept in sync with the staging source of truth platform/backup/minio-credentials.sops.yaml and the Proxmox host ansible-vault.

Reconciled by its own non-gating Flux Kustomization clusters/base/backup.yaml (dependsOn: platform-config, wait:false) — a backup controller must never gate the platform graph.

Backup scope (what's included vs excluded)

Two daily Schedules (cadence ${VELERO_BACKUP_SCHEDULE}, retention ${VELERO_RETENTION}):

Schedule	Namespaces	Volumes (kopia FSB)
daily	ALL except monitoring, unifi	all PVC data (defaultVolumesToFsBackup:true, opt-out)
daily-resources-only	monitoring, unifi	none (defaultVolumesToFsBackup:false) — resources only

Excluded volume data (reconstructable, per the sizing decision):

• monitoring — Prometheus TSDB PVC (ephemeral) + Loki 72h-log PVC. Grafana/Alertmanager are emptyDir (no PVC); Grafana dashboards are GitOps-provisioned.
• unifi — the ~7.4 GiB KubeVirt VM disk (huge; UniFi is protected by its own config export).

Their Kubernetes resources are still captured (by daily-resources-only) to aid DR.

Included (the irreplaceable ~6 GiB): every other namespace's PVC data via kopia — Nextcloud data, Gitea, Plex/*arr config, PiHole, and the CNPG Postgres PVCs. (CNPG DBs additionally have native Barman PITR to the cnpg bucket — see the DB manifests.)

Post-deploy (PM)

• velero backup-location get → default Available.
• velero backup create --from-schedule daily → objects land under s3://velero/.
• DR drill (R-STATE-03, Phase-4 gate): velero restore create --from-backup <name> into a scratch namespace and verify PVC data restores via the node-agent.