Go to file
Xun Jiang/Bruce Jiang 2dbfbc29e8
Merge pull request #9214 from weeix/patch-1
clarify VolumeSnapshotClass error for mismatched driver/provisioner
2025-09-03 15:12:09 +08:00
.github Bump actions/checkout from 4 to 5 2025-08-12 04:06:54 +00:00
assets fix: Typos and add more spell checking rules to CI (#6415) 2023-07-21 17:25:24 -04:00
changelogs feat: Permit specifying annotations for the BackupPVC 2025-08-29 10:10:41 +02:00
cmd Add E2E test cases for backup VolumeInfo feature. 2024-02-22 16:18:55 +08:00
config Make ResticIdentifier optional for kopia repositories (#8987) 2025-07-24 22:25:09 -04:00
design move implemented design for 1.17 2025-08-27 14:40:49 +08:00
examples fix: update mc command in minio-deployment example (#8982) 2025-05-28 09:42:26 -04:00
hack bump up kopia to v0.21.1 2025-07-22 15:56:04 +08:00
internal Change the CreateFileToPod function's OS parameter as the E2E pass-in value. 2025-08-21 09:34:06 +08:00
pkg clarify VolumeSnapshotClass error for mismatched driver/provisioner 2025-09-02 18:31:13 -05:00
site feat: Permit specifying annotations for the BackupPVC 2025-08-29 10:10:41 +02:00
test Add E2E cases for node-agent-configmap. 2025-09-02 15:03:20 +08:00
third_party/kubernetes/pkg/kubectl/cmd remove hardcoded svc, netpol mappings 2020-01-16 19:16:45 -07:00
tilt-resources Update CSI document. Remove the CSI plugin verifier. 2024-04-12 13:51:20 +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 .config/ to gitignore 2025-06-06 10:54:11 -04:00
.golangci.yaml chore: enable exptostd linter (#9086) 2025-07-17 17:16:00 -04:00
.goreleaser.yml Add s390x binary support (#7505) 2025-04-04 09:39:01 -04:00
ADOPTERS.md Update CloudCasa description in adopters list. 2024-02-18 12:18:40 -05:00
CHANGELOG.md add 1.15 changelog 2024-10-22 18:30:26 +08:00
CODE_OF_CONDUCT.md Fix the problems found by codespell 2024-05-24 13:32:54 +08:00
CONTRIBUTING.md Update links to point to main branch (#2915) 2020-09-09 12:11:57 -07:00
Dockerfile bump up kopia to v0.21.1 2025-07-22 15:56:04 +08:00
Dockerfile-Windows bump up kopia to v0.21.1 2025-07-22 15:56:04 +08:00
GOVERNANCE.md Update GOVERNANCE.md 2024-07-10 23:44:55 -07:00
LICENSE Initial commit 2017-08-02 13:27:17 -04:00
MAINTAINERS.md Remove Ming Qiu from maintainers 2024-11-16 17:11:32 +08:00
Makefile The backup and restore data mover node selection. 2025-07-01 16:26:12 +08:00
OWNERS Support more PROW commands. (#7784) 2024-05-14 14:19:25 -04:00
README.md update 1.17 readme and implemented design 2025-08-27 14:03:26 +08:00
ROADMAP.md Update ROADMAP.md with link to wiki and wiki guidance 2022-04-28 15:25:20 +03:00
SECURITY.md Replace security@vmware.com with velero-security.pdl@broadcom.com. (#8954) 2025-05-22 09:47:05 -04:00
SUPPORT.md Update links to point to main branch (#2915) 2020-09-09 12:11:57 -07:00
Tiltfile bump up kopia to v0.21.1 2025-07-22 15:56:04 +08:00
go.mod Use 1.24 instead of v1.24.0, and remove toolchain. 2025-07-24 11:30:08 +08:00
go.sum Merge branch 'main' into bump-up-kopia-0.21.1 2025-07-22 13:42:37 +08:00
netlify.toml Revert PR #6907 as site is not deploying (#6981) 2023-10-23 12:14:26 -04:00
restore-hooks_product-requirements.md fix: Typos and add more spell checking rules to CI (#6415) 2023-07-21 17:25:24 -04: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.17 1.18-latest 1.31.7, 1.32.3, and 1.33.1
1.16 1.18-latest 1.31.4, 1.32.3, and 1.33.0
1.15 1.18-latest 1.28.8, 1.29.8, 1.30.4 and 1.31.1
1.14 1.18-latest 1.27.9, 1.28.9, and 1.29.4
1.13 1.18-latest 1.26.5, 1.27.3, 1.27.8, and 1.28.3
1.12 1.18-latest 1.25.7, 1.26.5, 1.26.7, and 1.27.3
1.11 1.18-latest 1.23.10, 1.24.9, 1.25.5, and 1.26.1

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 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.