Backblaze B2 backup location
How every backed-up app gets a restic target on Backblaze B2 — the k8up Schedule declares intent, the Crossplane TofuWorkspace composition provisions the bucket and a bucket-scoped application key, and External Secrets fences the one human-managed credential to the workspace namespaces.
Backups (component)
Reusable Kustomize component that wires two per-app k8up Schedules into the app's namespace — one Restic repository on Hetzner Object Storage, one on Backblaze B2, daily, with the standard retention.
backups-cnpg (component)
Reusable Kustomize component that adds a k8up PreBackupPod to an app's namespace, so every backup run starts with a pg_dump of the app's CloudNative-PG cluster streamed straight into the Restic snapshot as a plain .sql file.
k8up
Kubernetes backup operator using Restic and S3-compatible storage.
PostgreSQL backup & restore
Ad-hoc dumps and restores against a CloudNativePG cluster, and the full restore of a database from a k8up Restic snapshot.
Three-tier backups, end-to-end
How a byte written to a Longhorn PVC ends up in three places — warm (Restic to Hetzner and Backblaze), hot (Syncthing to the off-site Synology), cold (encrypted WD Elements drives) — and what it takes to restore from each.
Volume restore
Restoring a persistent volume from a k8up Restic snapshot, with the variants for MongoDB, the SILO object store and Longhorn's local snapshots.