All guides
Back up Kubernetes to NordenVault
Back up Kubernetes cluster resources and persistent volumes to EU-hosted storage using Velero.
Prerequisites
- A NordenVault account with S3 credentials
- A running Kubernetes cluster with kubectl configured
- Velero CLI installed locally
- Helm (optional, for Helm-based installation)
Install the Velero CLI
# macOS
brew install velero
# Linux
curl -sL https://github.com/vmware-tanzu/velero/releases/download/v1.15.2/velero-v1.15.2-linux-amd64.tar.gz | tar xz
sudo mv velero-v1.15.2-linux-amd64/velero /usr/local/bin/Create credentials file
Create a file at /tmp/nordenvault-credentials:
[default]
aws_access_key_id = YOUR_ACCESS_KEY
aws_secret_access_key = YOUR_SECRET_KEYInstall Velero on the cluster
velero install \
--provider aws \
--plugins velero/velero-plugin-for-aws:v1.11.0 \
--bucket YOUR_BUCKET \
--prefix velero \
--secret-file /tmp/nordenvault-credentials \
--backup-location-config \
region=us-east-1,\
s3ForcePathStyle=true,\
s3Url=https://s3.nordenvault.comWait for Velero to start:
kubectl -n velero get pods
# Wait until the velero pod is RunningRun a backup
Back up the entire cluster
velero backup create full-backup
# Check status
velero backup describe full-backup
velero backup logs full-backupBack up a specific namespace
velero backup create staging-backup --include-namespaces stagingBack up with label selector
velero backup create app-backup --selector app=myappSchedule automated backups
# Daily backup at 2 AM UTC, retain for 7 days
velero schedule create daily-backup \
--schedule "0 2 * * *" \
--ttl 168h
# Weekly full backup, retain for 30 days
velero schedule create weekly-backup \
--schedule "0 3 * * 0" \
--ttl 720h
# List schedules
velero schedule getRestore
Restore from the latest backup
# List available backups
velero backup get
# Restore everything
velero restore create --from-backup full-backup
# Check restore status
velero restore describe full-backup-restoreRestore a specific namespace
velero restore create --from-backup full-backup \
--include-namespaces stagingRestore to a different namespace
velero restore create --from-backup staging-backup \
--namespace-mappings staging:staging-restoredDisaster recovery
To restore a cluster from scratch (e.g. after a total cluster loss), install Velero on the new cluster pointing to the same NordenVault bucket. Velero will discover existing backups automatically:
# On the new cluster, install Velero with the same config
velero install \
--provider aws \
--plugins velero/velero-plugin-for-aws:v1.11.0 \
--bucket YOUR_BUCKET \
--prefix velero \
--secret-file /tmp/nordenvault-credentials \
--backup-location-config \
region=us-east-1,\
s3ForcePathStyle=true,\
s3Url=https://s3.nordenvault.com
# List backups from the previous cluster
velero backup get
# Restore
velero restore create --from-backup full-backupWhat Velero backs up
- All Kubernetes resources (deployments, services, configmaps, secrets, CRDs)
- Persistent volume snapshots (with CSI plugin)
- Namespace-level metadata and RBAC
Velero stores backup manifests and resource data as tarballs in your NordenVault bucket. Persistent volume snapshots depend on your cluster's CSI driver.