vmware-tanzu
/
velero
mirror of https://github.com/vmware-tanzu/velero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
1,686 Commits
33 Branches
161 Tags
105 MiB
Go 94.6%
SCSS 3.4%
Shell 0.6%
HTML 0.5%
Makefile 0.4%
Other 0.5%
 
 
 
 
 
 
Go to file
Scott Seago 970f17c1ef If includeClusterResources is nil/auto, pull in necessary CRDs (#1831) 
Related issue: https://github.com/heptio/velero/issues/1830

This accomplishes everything
that's needed, although there might be room for improvement in avoiding
a GET call for matching CRDs for each resource backed up. An alternative
could be a single call to get all CRDs prior to iterating over resources
and passing this into the backupResource function.

Signed-off-by: Scott Seago <sseago@redhat.com>
 		2019-10-17 12:31:04 -06:00
.github/ISSUE_TEMPLATE Add features package (#1849) 2019-09-18 10:57:04 -06:00
changelogs If includeClusterResources is nil/auto, pull in necessary CRDs (#1831) 2019-10-17 12:31:04 -06: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 Reorg install and plugin docs (#1916) 2019-10-02 16:24:42 -04:00
hack migrate images to docker hub (#1966) 2019-10-16 11:03:23 -06:00
pkg If includeClusterResources is nil/auto, pull in necessary CRDs (#1831) 2019-10-17 12:31:04 -06:00
site fix links to azure setup instructions (#1963) 2019-10-15 14:46:36 -06: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 Add support for GKE Workload Identity (#1810) 2019-10-03 13:45:18 -07: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 travis: re-add ci-check (#1968) 2019-10-16 11:38:52 -06:00
CHANGELOG.md Updates for org move to vmware-tanzu (#1920) 2019-09-30 17:26:56 -04:00
CODE_OF_CONDUCT.md Update to CoC (#1955) 2019-10-09 16:11:03 -06: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 Add support for GKE Workload Identity (#1810) 2019-10-03 13:45:18 -07: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 migrate images to docker hub (#1966) 2019-10-16 11:03:23 -06:00
README.md Reorg install and plugin docs (#1916) 2019-10-02 16:24:42 -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. You can run Velero with a cloud provider 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, 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.