Go to file
Tiger Kaovilai 3f4b258dee defer ctxCancel
Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com>
2023-04-16 13:33:43 -04:00
.github Bumpup upgrade test path for v1.11 2023-04-07 07:21:40 +00:00
assets
changelogs Add changelog for v1.11. 2023-04-07 15:19:05 +08:00
cmd Enable staticcheck linter. Disable check for folder /pkg and /test by now. 2023-01-20 13:52:13 +08:00
config Modify new scope resource filters name. 2023-04-06 18:11:55 +08:00
design Modify README compatibility matrix, and move the implemented design into Implemented directory. (#6087) 2023-04-07 10:56:04 +08:00
examples
hack Merge branch 'main' into update_golang_version_new 2023-04-04 05:56:05 +00:00
internal defer ctxCancel 2023-04-16 13:33:43 -04:00
pkg cancel ctx in nil, err returns 2023-04-16 13:06:13 -04:00
site Add v1.11 document. 2023-04-07 09:32:22 +08:00
test defer ctxCancel 2023-04-16 13:33:43 -04:00
third_party/kubernetes/pkg/kubectl/cmd
tilt-resources remove restic from code 2022-10-13 13:45:32 +08:00
.dockerignore
.gitignore Modify new scope resource filters name. 2023-04-06 18:11:55 +08:00
.goreleaser.yml Fix tag release error 2022-06-14 09:34:05 +00:00
ADOPTERS.md add OADP to adopters list 2022-08-22 11:37:15 -04:00
CHANGELOG.md Amend doc 1.9 version 2022-06-14 10:22:27 +08:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Dockerfile Update Golang version to v1.19 for branch main. 2023-04-04 12:00:19 +08:00
GOVERNANCE.md
LICENSE
MAINTAINERS.md Reformat table in the document 2023-01-18 11:11:16 +08:00
Makefile Modify golangci.yaml file. Resolve found lint issues. (#6008) 2023-03-24 12:15:08 +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
SUPPORT.md
Tiltfile Update Golang version to v1.19 for branch main. 2023-04-04 12:00:19 +08:00
go.mod Handle backup of volume by resource policies (#5901) 2023-03-21 14:39:25 +08:00
go.sum `go get k8s.io/client-go@v0.25.6 && go mod tidy` 2023-02-23 16:41:29 -05:00
golangci.yaml Modify golangci.yaml file. Resolve found lint issues. (#6008) 2023-03-24 12:15:08 +08:00
netlify.toml
restore-hooks_product-requirements.md

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.