This namespace contains the configuration for the cluster backup and restore solution velero.
Velero is an open source tool to safely backup and restore, perform disaster recovery, and migrate Kubernetes cluster resources and persistent volumes.
- velero/crds/kustomizations.yaml - CRDs required by velero
- velero/velero.yaml - HelmRelease for velero
(credit billimek)
In order to restore a given workload, the follow steps should work:
- A backup should already be created either via:
- a global backup (e.g. a scheduled backup),
- or via a backup created using a label selector (that's present on the deployment, pv, & pvc) for the application, e.g.
velero backup create test-minecraft --selector "app=mc-test-minecraft" --wait
- <Do whatever action results in the active data getting lost (e.g.
kubectl delete hr mc-test)> - Delete the unwanted new data & associate Deployment/StatefulSet/Daemonset, e.g.
kubectl delete deployment mc-test-minecraft && kubectl delete pvc mc-test-minecraft-datadir - Restore from restic the backup with only the label selector, e.g.
velero restore create --from-backup test-minecraft --selector "app=mc-test-minecraft" --wait
- This should not interfere with the HelmRelease or require scaling helm-operator
- You don't need to worry about adding labels to the HelmRelease or backing-up the helm secret object