Go to file
Wenkai Yin(尹文开) 9f2f563568 Add data mover related options in CLI
Add data mover related options in CLI

Fixes #6128

Signed-off-by: Wenkai Yin(尹文开) <yinw@vmware.com>
2023-06-07 16:34:40 +08:00
.github Add data mover CRD under v2alpha1 (#6176) 2023-05-16 15:09:54 -04:00
assets Add logo assets 2021-04-19 13:45:09 -07:00
changelogs Add data mover related options in CLI 2023-06-07 16:34:40 +08:00
cmd Enable staticcheck linter. Disable check for folder /pkg and /test by now. 2023-01-20 13:52:13 +08:00
config Add data mover CRD under v2alpha1 (#6176) 2023-05-16 15:09:54 -04:00
design Merge pull request #5968 from Lyndon-Li/velero-data-movement-design 2023-05-24 08:33:20 +08:00
examples 📖 use correct link to the minio.md (#3071) 2020-11-12 16:08:26 -08:00
hack Skip running unit test for pkg/builder package 2023-05-29 09:26:12 +08:00
internal Enable errcheck linter and resolve found issues. 2023-04-28 09:33:42 +08:00
pkg Add data mover related options in CLI 2023-06-07 16:34:40 +08:00
site Add files via upload 2023-05-23 11:56:21 -04:00
test/e2e Prepare E2E test of data movement feature 2023-06-05 01:49:08 +00:00
third_party/kubernetes/pkg/kubectl/cmd remove hardcoded svc, netpol mappings 2020-01-16 19:16:45 -07:00
tilt-resources Change rbac.authorization.k8s.io/v1beta1 to rbac.authorization.k8s.io/v1 in deployment.yml 2023-05-09 16:04:53 +05:30
.dockerignore Refactor image builds to use buildx for multi arch image building (#2754) 2020-08-04 11:40:05 -07:00
.gitignore Add required footer links and update .gitignore 2023-05-15 09:33:08 -04:00
.goreleaser.yml Fix goreleaser issues and add new goreleaser action. 2023-04-11 17:03:20 +08:00
ADOPTERS.md Add PITS Global Data Recovery Services to the list of adopters 2023-05-23 11:59:25 -04: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 Modify Docker's maintainer label. (#6238) 2023-05-09 09:27:32 +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 Reformat table in the document 2023-01-18 11:11:16 +08:00
Makefile Improve the unit test coverage of pkg/cmd/server package (#6342) 2023-06-05 23:15:24 +08:00
README.md Modify README compatibility matrix, and move the implemented design into Implemented directory. (#6087) 2023-04-07 10:56:04 +08: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 Add data mover CRD under v2alpha1 (#6176) 2023-05-16 15:09:54 -04:00
go.mod bump up kopia v0.13.0 2023-05-15 07:23:38 +08:00
go.sum bump up kopia v0.13.0 2023-05-15 07:23:38 +08:00
golangci.yaml Enable errcheck linter and resolve found issues. 2023-04-28 09:33:42 +08: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 GitHub release (latest SemVer)

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.11 1.18-latest 1.23.10, 1.24.9, 1.25.5, and 1.26.1
1.10 1.18-latest 1.22.5, 1.23.8, 1.24.6 and 1.25.1
1.9 1.18-latest 1.20.5, 1.21.2, 1.22.5, 1.23, and 1.24
1.8 1.18-latest

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.

For each release, Velero maintainers run the test to ensure the upgrade path from n-2 minor release. For example, before the release of v1.10.x, the test will verify that the backup created by v1.9.x and v1.8.x can be restored using the build to be tagged as v1.10.x.