debcbd2f8e
* fix: rename the PV if VolumeSnapshotter has modified the PV name When VolumeSnapshotter sets the PV name via SetVolumeID and PV is not there in the cluster, velero does not rename the PV. Which causes the pvc to be in the lost state as pvc points to the old PV but pv object has been renamed by VolumeSnapshotter. Signed-off-by: Pawan <pawan@mayadata.io> * adding a test case for pv rename Signed-off-by: Pawan <pawan@mayadata.io>
Overview
Velero (formerly Heptio Ark) gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes. You can run Velero with a public cloud platform or on-premises. Velero lets you:
- Take backups of your cluster and restore in case of loss.
- Migrate cluster resources to other clusters.
- Replicate your production cluster to development and testing clusters.
Velero consists of:
- A server that runs on your cluster
- A command-line client that runs locally
Documentation
The documentation provides a getting started guide and information about building from source, architecture, extending Velero, and more.
Please use the version selector at the top of the site to ensure you are using the appropriate documentation for your version of Velero.
Troubleshooting
If you encounter issues, review the troubleshooting docs, file an issue, or talk to us on the #velero channel on the Kubernetes Slack server.
Contributing
If you are ready to jump in and test, add code, or help with documentation, follow the instructions on our Start contributing documentation for guidance on how to setup Velero for development.
Changelog
See the list of releases to find out about feature changes.