f3d36afd3a
* remove refs to pre-v1.0 velero versions from docs Signed-off-by: Steve Kriss <krisss@vmware.com> |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| changelogs | ||
| cmd | ||
| docs | ||
| examples | ||
| hack | ||
| pkg | ||
| third_party/kubernetes/pkg/kubectl/cmd | ||
| vendor | ||
| .gitignore | ||
| .goreleaser.yml | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Dockerfile-fsfreeze-pause | ||
| Dockerfile-velero | ||
| Dockerfile-velero-restic-restore-helper | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| SUPPORT.md | ||
README.md
Overview
Velero (formerly Heptio Ark) gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes. Velero lets you:
- Take backups of your cluster and restore in case of loss.
- Copy cluster resources to other clusters.
- Replicate your production environment for development and testing environments.
Velero consists of:
- A server that runs on your cluster
- A command-line client that runs locally
You can run Velero in clusters on a cloud provider or on-premises. For detailed information, see Compatible Storage Providers.
Installation
We strongly recommend that you use an official release of Velero. The tarballs for each release contain the command-line client and version-specific sample YAML files for deploying Velero to your cluster. Follow the instructions under the Install section of our documentation to get started.
The code and sample YAML files in the master branch of the Velero repository are under active development and are not guaranteed to be stable. Use them at your own risk!
More information
The documentation provides a getting started guide, plus 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
Thanks for taking the time to join our community and start contributing!
Feedback and discussion are available on the mailing list.
Before you start
- Please familiarize yourself with the Code of Conduct before contributing.
- See CONTRIBUTING.md for instructions on the developer certificate of origin that we require.
- Read how we're using ZenHub for project and roadmap planning
Pull requests
- We welcome pull requests. Feel free to dig through the issues and jump in.
Changelog
See the list of releases to find out about feature changes.