apiVersion: v2
name: bp-velero
description: |
  Catalyst Blueprint umbrella chart for Velero. Depends on the upstream
  `velero` chart (vmware-tanzu/helm-charts) as a Helm subchart so
  `helm dependency build` pulls the upstream payload into this artifact.
  Catalyst-curated values flow into the upstream subchart under the
  `velero:` key in values.yaml.

  Velero is the per-host-cluster backup engine. Per docs/omantel-
  handover-wbs.md §3 + ADR-0001 §13 (S3-aware app architecture rule),
  Velero on a Hetzner Sovereign writes its backups DIRECTLY to Hetzner
  Object Storage (https://<region>.your-objectstorage.com), NOT
  SeaweedFS. SeaweedFS is reserved as a POSIX→S3 buffer for legacy
  POSIX-only writers and is not in the minimal Sovereign set.

  Per #425 the chart is vendor-AGNOSTIC: per-Sovereign overlays wire
  the BackupStorageLocation via Flux `valuesFrom` against the canonical
  `flux-system/object-storage` Secret — the Sealed Secret name no
  longer leaks the cloud-provider name. The umbrella's
  templates/objectstorage-credentials.yaml synthesises a velero-
  namespace Secret with the AWS-CLI INI `cloud` key the upstream chart
  expects via existingSecret. Adding a future AWS / Azure / GCP / OCI
  Sovereign requires only a sibling `infra/<provider>/` Tofu module —
  this chart Just Works.
type: application
version: 1.2.1
appVersion: "1.18.0"
keywords: [catalyst, blueprint, velero, backup, disaster-recovery]
maintainers:
  - name: OpenOva Catalyst
    email: catalyst@openova.io

# Pinned to vmware-tanzu/velero 12.0.1 (appVersion 1.18.0) — current
# stable on 2026-04-29. Per docs/INVIOLABLE-PRINCIPLES.md #4 (never
# hardcode) the version is operator-bumpable via PR + Blueprint release.
dependencies:
  - name: velero
    version: "12.0.1"
    repository: "https://vmware-tanzu.github.io/helm-charts"
