Velero: Backing Up Kubernetes, Not Just Volumes

Tue, 24 Sep 2024 11:15:00 +0000

The first time I lost a Kubernetes namespace to a fat-fingered kubectl delete namespace, I discovered that my “backups” covered exactly the wrong half of the problem. The persistent volumes were sitting safely on a ZFS pool with nightly snapshots. The Deployments, Services, Ingresses, ConfigMaps, Secrets and the dozen other objects that actually described how those volumes were supposed to be used were gone, and rebuilding them from memory and half-remembered YAML took the better part of an evening. A PersistentVolume without the Deployment that mounts it is just an orphaned disk; the cluster state is the application, and it needs backing up as deliberately as the data does.

Velero - vo.rs

Velero: Backing Up Kubernetes, Not Just Volumes