This is the documentation for the latest development version of Velero. Both code and docs may be unstable, and these docs are not guaranteed to be up to date or correct. See the latest version.
Velero provides best effort support through the process on this page for the current version of Velero and n-1 Velero version, including all patch releases in the supported minor releases. For example, if the current version is 1.9, the Velero maintainers would offer best effort support for v1.9 and v1.8. If you have a question about a previous Velero version (for example, 1.7), please note that maintainers may ask you to upgrade to a supported version before doing any investigation into your issue.
For more information about Velero testing and supported Kubernetes versions, see Velero’s compatibility matrix.
The Velero maintainers use a weekly rotation to manage community support. Each week, a different maintainer is the point person for responding to incoming support issues via Slack, GitHub, and the Google group. The point person is not expected to be on-call 24x7. Instead, they choose one or more hour(s) per day to be available/responding to incoming issues. They will communicate to the community what that time slot will be each week.
We will update the public Slack channel’s topic to indicate that you are the point person for the week, and what hours you’ll be available.
#velero-devpublic Slack channels in Kubernetes org
Generally speaking, new GitHub issues will fall into one of several categories. We use the following process for each:
Needs investigationlabel to indicate additional work needed to truly understand the problem or the root cause.
Needs Infolabel to indicate an issue is waiting for information from the user. Remove/re-add the label as needed.
status/not-reproducibleto indicate the status.