Go to file
qiuming 3ca580b7d9
Generate v1.9.3 changelog (#5538)
Signed-off-by: Ming <mqiu@vmware.com>
2022-11-03 14:19:07 +08:00
.github Change the name of changelog file and update code/doc to pass checking 2022-10-21 18:15:23 +08:00
assets Add logo assets 2021-04-19 13:45:09 -07:00
changelogs Generate v1.9.3 changelog (#5538) 2022-11-03 14:19:07 +08:00
cmd changes according to review comments 2022-05-09 15:55:14 +08:00
config update k8s.io dependencies to 0.24.0 2022-10-21 13:49:18 +08:00
design Change the name of changelog file and update code/doc to pass checking 2022-10-21 18:15:23 +08:00
examples 📖 use correct link to the minio.md (#3071) 2020-11-12 16:08:26 -08:00
hack Fix CVE-2022-1962 by bumping up golang verison to 1.17.13 (#5286) 2022-09-13 18:48:42 +08:00
internal fix: delete empty backups 2022-04-12 13:13:56 +03:00
pkg Enhance the restore priorities list to support specifying the low prioritized resources that need to be restored in the last 2022-11-02 14:26:10 +08:00
site Make CSI snapshot creation timeout configurable for backup and schedule. 2022-08-08 15:09:32 +00:00
test/e2e Fix code spell check fail 2022-09-07 02:29:00 +00:00
third_party/kubernetes/pkg/kubectl/cmd remove hardcoded svc, netpol mappings 2020-01-16 19:16:45 -07:00
tilt-resources Correct the environment variable for azure credential file (#4313) 2021-11-03 12:47:49 -04:00
.dockerignore Refactor image builds to use buildx for multi arch image building (#2754) 2020-08-04 11:40:05 -07:00
.gitignore Implement `velero debug` (#4022) 2021-08-30 18:37:18 -07:00
.goreleaser.yml Fix tag release error 2022-06-14 09:53:49 +00:00
ADOPTERS.md Add CloudCasa to "Adopters of Velero" section on velero.io (#4588) 2022-02-17 08:57:02 +08:00
CHANGELOG.md Amend doc 1.9 version 2022-06-14 10:22:27 +08: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 Bump up the distroless image to the latest version (#5500) 2022-10-27 10:24:06 +08: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 Propose Shubham Pampattiwar as a maintainer 2022-05-19 11:35:20 -04:00
Makefile Delete orphan CSI snapshots in backup sync controller 2022-05-05 10:54:34 +08:00
README.md Update wording and add more useful links 2022-05-16 09:39:54 -04:00
ROADMAP.md Update ROADMAP.md with link to wiki and wiki guidance 2022-04-28 15:25:20 +03: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 Convert Pod Volume Restore resource/controller to the Kubebuilder framework 2022-04-26 16:23:38 +08:00
go.mod Fix CVE-2022-27191 2022-10-24 09:57:40 +00:00
go.sum Fix CVE-2022-27191 2022-10-24 09:57:40 +00: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.

Velero compatibility matrix

The following is a list of the supported Kubernetes versions for each Velero version.

Velero version Expected Kubernetes version compatibility Tested on Kubernetes version
1.9 1.16-latest 1.20.5, 1.21.2, 1.22.5, 1.23, and 1.24
1.8 1.16-latest
1.6.3-1.7.1 1.12-latest
1.60-1.6.2 1.12-1.21
1.5 1.12-1.21
1.4 1.10-1.21

Velero supports IPv4, IPv6, and dual stack environments. Support for this was tested against Velero v1.8.

The Velero maintainers are continuously working to expand testing coverage, but are not able to test every combination of Velero and supported Kubernetes versions for each Velero release. The table above is meant to track the current testing coverage and the expected supported Kubernetes versions for each Velero version. If you have a question about test coverage before v1.9, please reach out in the #velero-users Slack channel.

If you are interested in using a different version of Kubernetes with a given Velero version, we'd recommend that you perform testing before installing or upgrading your environment. For full information around capabilities within a release, also see the Velero release notes or Kubernetes release notes. See the Velero support page for information about supported versions of Velero.