704bf01fab
The command to check for an existing release branch only checked for local branches. We should be considering both local and remote branches before cherry-picking commits for the new release. This change checks for existing local and remote release branches and creates or updates them accordingly. * If a remote branch exists, but a local branch does not, checkout the remote branch and track it. * If the remote branch and local branch exists, checkout the local branch and ensure that the latest commits from the remote are pulled. * Otherwise, if the remote branch does not exist, create it locally if needed. This also handles the case where an existing release branch may be tracked in multiple remotes as the remote to use is explicitly stated. Signed-off-by: Bridget McErlean <bmcerlean@vmware.com>
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.