Go to file
JenTing Hsiao e4dd55566d Update CI codespell check
update the path of crds.go to ignore it.

Signed-off-by: JenTing Hsiao <jenting.hsiao@suse.com>
2021-07-27 17:55:34 -04:00
.github Update CI codespell check 2021-07-27 17:55:34 -04:00
assets Add logo assets 2021-04-19 13:45:09 -07:00
changelogs Add changelog 2021-07-27 17:55:34 -04:00
cmd Updates for org move to vmware-tanzu (#1920) 2019-09-30 17:26:56 -04:00
config Run script to generate both v1beta1 and v1 CRDs 2021-07-27 17:55:10 -04:00
design Add the design for `velero debug` (#3973) 2021-07-21 22:29:49 -07:00
examples 📖 use correct link to the minio.md (#3071) 2020-11-12 16:08:26 -08:00
hack Update script to generate both v1beta1 and v1 CRDs 2021-07-27 17:55:10 -04:00
internal Allow registry to be configured at build time 2021-07-14 15:42:53 -04:00
pkg Add new flag --crds-version of default CRD version to generated 2021-07-27 17:55:34 -04:00
site Update upgrade instructions to reference v1.6.2 (#3977) 2021-07-22 21:28:20 +08:00
test/e2e Fixing multipleNamespaceTest bug - Missing expect statement in test (#3983) 2021-07-27 15:32:36 +08:00
third_party/kubernetes/pkg/kubectl/cmd remove hardcoded svc, netpol mappings 2020-01-16 19:16:45 -07:00
tilt-resources Add Tilt configuration to debug using Delve (#3189) 2021-01-22 10:12:04 +08:00
.dockerignore Refactor image builds to use buildx for multi arch image building (#2754) 2020-08-04 11:40:05 -07:00
.gitignore Add Tilt configs (#3119) 2020-12-08 13:42:03 -05:00
.goreleaser.yml Allow registry to be configured at build time 2021-07-14 15:42:53 -04:00
ADOPTERS.md Adding Replicated logo to adopters page - take 2 2021-07-15 07:40:31 -04:00
CHANGELOG.md Add changelog and docs for v1.6.0 2021-04-12 16:00:34 -04:00
CODE_OF_CONDUCT.md Update to latest covenant coc (#3076) 2020-11-19 16:07:38 -05:00
CONTRIBUTING.md Update links to point to main branch (#2915) 2020-09-09 12:11:57 -07:00
Dockerfile Allow registry to be configured at build time 2021-07-14 15:42:53 -04:00
GOVERNANCE.md Update links to point to main branch (#2915) 2020-09-09 12:11:57 -07:00
LICENSE Initial commit 2017-08-02 13:27:17 -04:00
MAINTAINERS.md Nominate Wenkai Yin to become a maintainer 2021-07-14 13:51:45 -04:00
Makefile Fix push-build-image target 2021-07-16 18:14:56 -04:00
PROJECT Convert manifests + BSL api client to kubebuilder (#2561) 2020-06-24 12:55:18 -04:00
README.md Add CII Best Practices badge to README (#2880) 2020-08-31 17:33:03 -04:00
ROADMAP.md Proposed 1.7.0 roadmap (#3537) 2021-03-08 17:04:30 -08:00
SECURITY.md Rename security policy file to show up accurately in the GitHub UI (#2879) 2020-08-31 12:10:09 -04:00
SUPPORT.md Update links to point to main branch (#2915) 2020-09-09 12:11:57 -07:00
Tiltfile Upgrade restic from v0.9.6 to v0.12.0 (#3528) 2021-03-11 13:11:23 -05:00
go.mod Update k8s libraries to latest patch version (#3953) 2021-07-15 10:08:54 +08:00
go.sum Update k8s libraries to latest patch version (#3953) 2021-07-15 10:08:54 +08:00
golangci.yaml Add linter (#2615) 2020-06-30 12:51:10 -04:00
netlify.toml v1.5 blog post (#2940) 2020-09-16 17:56:47 -04:00
restore-hooks_product-requirements.md Create restore-hooks_product-requirements.md (#2699) 2020-08-12 16:13:52 -07:00

README.md

100

Build Status CII Best Practices

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.