Go to file
KubeKween c284746aab
Blog post: new GH org (#1897)
* Blog post: new GH org

Signed-off-by: Carlisia <carlisia@vmware.com>
2019-10-01 11:08:28 -07:00
.github/ISSUE_TEMPLATE Add features package (#1849) 2019-09-18 10:57:04 -06:00
changelogs sync controller: replace revision file with full diff each interval (#1892) 2019-09-27 16:23:11 -04:00
cmd Updates for org move to vmware-tanzu (#1920) 2019-09-30 17:26:56 -04:00
design Plan for moving plugin repos (#1870) 2019-09-19 14:06:15 -06:00
examples fix Deployments in examples for apps/v1 selector requirement (#1684) 2019-07-19 11:40:47 -06:00
hack Prevent master from being tagged as latest (#1922) 2019-10-01 12:04:57 -06:00
pkg Updates for org move to vmware-tanzu (#1920) 2019-09-30 17:26:56 -04:00
site Blog post: new GH org (#1897) 2019-10-01 11:08:28 -07:00
third_party/kubernetes/pkg/kubectl/cmd shortcut expander: use discovery helper's cached resource list 2019-05-07 12:23:45 -06:00
vendor Generate CRDs with structural schema (#1885) 2019-09-23 10:25:48 -06:00
.gitignore Docs updates - extra finishing touches (#1516) 2019-05-28 12:42:27 -04:00
.goreleaser.yml Updates for org move to vmware-tanzu (#1920) 2019-09-30 17:26:56 -04:00
.travis.yml Updates for org move to vmware-tanzu (#1920) 2019-09-30 17:26:56 -04:00
CHANGELOG.md Updates for org move to vmware-tanzu (#1920) 2019-09-30 17:26:56 -04:00
CODE_OF_CONDUCT.md Rename Ark to Velero!!! 2019-02-04 17:35:22 -05:00
CONTRIBUTING.md remove all remaining legacy Ark references (#1415) 2019-04-29 12:33:54 -07:00
Dockerfile-fsfreeze-pause change base images to ubuntu:bionic 2019-05-15 12:56:20 -07:00
Dockerfile-fsfreeze-pause-ppc64le minor fixes 2019-07-09 06:02:14 +00:00
Dockerfile-velero record restic backup progress in PodVolumeBackup (#1821) 2019-09-10 11:28:19 -07:00
Dockerfile-velero-ppc64le record restic backup progress in PodVolumeBackup (#1821) 2019-09-10 11:28:19 -07:00
Dockerfile-velero-restic-restore-helper change base images to ubuntu:bionic 2019-05-15 12:56:20 -07:00
Dockerfile-velero-restic-restore-helper-ppc64le minor fixes 2019-07-09 06:02:14 +00:00
Gopkg.lock Generate CRDs with structural schema (#1885) 2019-09-23 10:25:48 -06:00
Gopkg.toml GCP: support specifying Cloud KMS key name for backup storage locations (#1879) 2019-09-17 16:35:28 -04:00
LICENSE Initial commit 2017-08-02 13:27:17 -04:00
Makefile Updates for org move to vmware-tanzu (#1920) 2019-09-30 17:26:56 -04:00
README.md Updates for org move to vmware-tanzu (#1920) 2019-09-30 17:26:56 -04:00
SUPPORT.md Update mailing list in SUPPORT.md 2019-04-23 20:45:56 -07:00
heptio-images-fac92d2303ac.json.enc Add script for pushing container images via Travis (#1800) 2019-09-05 11:16:23 -06:00
netlify.toml add velero.io site content, move docs to under site/docs (#1489) 2019-05-17 10:56:03 -07:00

README.md

100

Build Status

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.
  • 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

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 velero command-line client. Follow the installation instructions 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

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.