Go to file
Xun Jiang/Bruce Jiang 9606df624f
Merge pull request #6784 from yanggangtony/node-agent-metrics-addr
Fix node-agent missing metrics-addr parms to define the server start. #6784
2023-10-13 14:28:45 +08:00
.github Add go clean in Dockerfile and action. 2023-09-28 20:30:05 +08:00
assets fix: Typos and add more spell checking rules to CI (#6415) 2023-07-21 17:25:24 -04:00
changelogs Fix node-agent missing metrics-addr parms to define the server start. 2023-10-13 03:33:18 +01:00
cmd Add license notes for velero-helper. 2023-08-31 14:07:34 +08:00
config issue 6861: fill repoIdentifier only for restic repo (#6872) 2023-09-27 16:49:35 -04:00
design Fix dep package describe and ci words spell. (#6924) 2023-10-09 12:12:14 +05:30
examples examples: Label the deployment to get it backed up (#6348) 2023-06-09 15:42:04 +08:00
hack Replace the base image with paketobuildpacks image (#6883) 2023-09-29 12:19:51 -04:00
internal Add missing file licences and do some clean works. 2023-09-29 04:25:01 +01:00
pkg Fix node-agent missing metrics-addr parms to define the server start. 2023-10-13 03:33:18 +01:00
site Merge pull request #6937 from blackpiglet/release_choco 2023-10-12 15:47:26 +08:00
test Fix dep package describe and ci words spell. (#6924) 2023-10-09 12:12:14 +05:30
third_party/kubernetes/pkg/kubectl/cmd remove hardcoded svc, netpol mappings 2020-01-16 19:16:45 -07:00
tilt-resources Add support for block volumes (#6680) 2023-09-28 09:44:46 -04:00
.dockerignore Refactor image builds to use buildx for multi arch image building (#2754) 2020-08-04 11:40:05 -07:00
.gitignore regex matchstring error parsing 2023-07-13 10:10:37 +05:30
.goreleaser.yml Fix goreleaser issues and add new goreleaser action. 2023-04-11 17:03:20 +08:00
ADOPTERS.md fix: Typos and add more spell checking rules to CI (#6415) 2023-07-21 17:25:24 -04:00
CHANGELOG.md Update the CHANGELOG.md 2023-07-21 09:25: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 Replace the base image with paketobuildpacks image (#6883) 2023-09-29 12:19:51 -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 Move Dave Smith-Uchida to Emeritus Maintainer 2023-09-26 10:58:31 +03:00
Makefile Add performance E2E test 2023-08-15 01:46:36 +00:00
README.md Update readme and move implemented designs 2023-08-18 12:02:41 +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 Update tilt ubuntu image to 22.04 to fix glibc issue 2023-07-03 08:03:37 +00:00
go.mod Make Kopia support Azure AD 2023-09-19 11:28:04 +08:00
go.sum Make Kopia support Azure AD 2023-09-19 11:28:04 +08:00
golangci.yaml Add performance E2E test 2023-08-15 01:46:36 +00:00
netlify.toml remove `site/` prefix from publish 2023-10-02 15:07:40 -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.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
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.