Velero is an open source tool to safely backup and restore, perform disaster recovery, and migrate Kubernetes cluster resources and persistent volumes.
Velero has two main components: a CLI, and a server-side Kubernetes deployment.
See the different options for installing the Velero CLI.
Kubernetes v1.16+, because this helm chart uses CustomResourceDefinition apiextensions.k8s.io/v1. This API version was introduced in Kubernetes v1.16.
This helm chart installs Velero version v1.15 https://velero.io/docs/v1.15/. See the #Upgrading section for information on how to upgrade from other versions.
When installing using the Helm chart, the provider's credential information will need to be appended into your values. The easiest way to do this is with the --set-file argument, available in Helm 2.10 and higher. See your cloud provider's documentation for the contents and creation of the credentials-velero file.
When using the Azure plug-in, requests and limits must be set. See vmware-tanzu/velero#3234 and vmware-tanzu/helm-charts#469 for details.
The default configuration values for this chart are listed in values.yaml.
See Velero's full official documentation. More specifically, find your provider in the Velero list of supported providers for specific configuration information and examples.
See the main README.md.
Note: You may add the flag --set cleanUpCRDs=true if you want to delete the Velero CRDs after deleting a release.
Please note that cleaning up CRDs will also delete any CRD instance, such as BackupStorageLocation and VolumeSnapshotLocation, which would have to be reconfigured when reinstalling Velero. The backup data in object storage will not be deleted, even though the backup instances in the cluster will.
Specify the necessary values using the --set key=value[,key=value] argument to helm install. For example,
helm install velero vmware-tanzu/velero \
--namespace <YOUR NAMESPACE> \
--create-namespace \
--set-file credentials.secretContents.cloud=<FULL PATH TO FILE> \
--set configuration.backupStorageLocation[0].name=<BACKUP STORAGE LOCATION NAME> \
--set configuration.backupStorageLocation[0].provider=<PROVIDER NAME> \
--set configuration.backupStorageLocation[0].bucket=<BUCKET NAME> \
--set configuration.backupStorageLocation[0].config.region=<REGION> \
--set configuration.volumeSnapshotLocation[0].name=<VOLUME SNAPSHOT LOCATION NAME> \
--set configuration.volumeSnapshotLocation[0].provider=<PROVIDER NAME> \
--set configuration.volumeSnapshotLocation[0].config.region=<REGION> \
--set initContainers[0].name=velero-plugin-for-<PROVIDER NAME> \
--set initContainers[0].image=velero/velero-plugin-for-<PROVIDER NAME>:<PROVIDER PLUGIN TAG> \
--set initContainers[0].volumeMounts[0].mountPath=/target \
--set initContainers[0].volumeMounts[0].name=pluginsUsers of zsh might need to put quotes around key/value pairs.
Add/update the necessary values by changing the values.yaml from this repository, then run:
helm install vmware-tanzu/velero --namespace <YOUR NAMESPACE> -f values.yaml --generate-nameIf a value needs to be added or changed, you may do so with the upgrade command. An example:
helm upgrade <RELEASE NAME> vmware-tanzu/velero --namespace <YOUR NAMESPACE> --reuse-values --set configuration.backupStorageLocation[0].provider=<NEW PROVIDER>We're no longer supporting Helm v2 since it was deprecated in November 2020.
If a value needs to be added or changed, you may do so with the upgrade command. An example:
helm upgrade vmware-tanzu/velero <RELEASE NAME> --reuse-values --set configuration.backupStorageLocation[0].provider=<NEW PROVIDER>Delete the CSI plugin. Because the Velero CSI plugin is already merged into the Velero, need to remove the existing CSI plugin InitContainer. Otherwise, the Velero server plugin would fail to start due to same plugin registered twice. CSI plugin has been merged into velero repo in v1.14 release. It will be installed by default as an internal plugin.
This version removes the nodeAgent.privileged field, you should use nodeAgent.containerSecurityContext.privileged instead
The instructions found here will assist you in upgrading from version v1.14.x to v1.15.
The instructions found here will assist you in upgrading from version v1.13.x to v1.14.
The instructions found here will assist you in upgrading from version v1.12.x to v1.13.
The instructions found here will assist you in upgrading from version v1.11.x to v1.12.
The instructions found here will assist you in upgrading from version v1.10.x to v1.11.
The instructions found here will assist you in upgrading from version v1.9.x to v1.10.
The instructions found here will assist you in upgrading from version v1.8.x to v1.9.
The instructions found here will assist you in upgrading from version v1.7.x to v1.8.
The instructions found here will assist you in upgrading from version v1.6.x to v1.7.
The instructions found here will assist you in upgrading from version v1.5.x to v1.6.
The instructions found here will assist you in upgrading from version v1.4.x to v1.5.
The instructions found here will assist you in upgrading from version v1.3.x to v1.4.
The instructions found here will assist you in upgrading from version v1.2.0 or v1.3.0 to v1.3.1.
The instructions found here will assist you in upgrading from version v1.0.0 or v1.1.0 to v1.2.0.
The instructions found here will assist you in upgrading from version v1.0.0 to v1.1.0.
Note: when you uninstall the Velero server, all backups remain untouched.
helm uninstall <RELEASE NAME> -n <YOUR NAMESPACE>Since from velero v1.10.0, it has supported both Restic and Kopia to do file-system level backup and restore, some configuration that contains the keyword Restic is not suitable anymore, which means from chart version 3.0.0 is not backward compatible, and we've done a configure filed name validation.