KrishhnaTandGitHub
6093ea050c
* e2e: fail the suite when a label filter selects no specs A label expression that matches nothing is reported as a pass. Ginkgo runs zero specs, prints SUCCESS!, and exits 0, so a run that tested nothing is indistinguishable from one that tested everything asked of it: $ GINKGO_LABELS='Basic && BackupsSync' make -C test/ run-e2e Ran 0 of 70 Specs in 0.001 seconds SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 70 Skipped That expression looks reasonable and selects nothing, because the backup sync case is labelled Backups rather than Basic. The same shape of mistake kept the VolumeGroupSnapshot case from running for months, where CSISnapshot did not select CSIVolumeGroupSnapshot because a bare token is matched by equality rather than as a substring. Pass --fail-on-empty, which ginkgo has supported for far longer than the version in go.mod, so the above now ends in: FAIL! - Detected no specs ran and --fail-on-empty is set It cannot affect a run that selects specs and then skips them at run time, which this suite does constantly on kind. The flag tests specs.CountWithoutSkip(), and that Skip field is set only while the label filter is applied, before anything runs; a Skip() call during a spec sets the spec's state instead. Checked all five label rows the kind workflow uses against every labelled Describe in the suite: the smallest selects two specs, so none of them starts failing. run-perf keeps the old behaviour. It takes its own labels for a different workload, and an empty selection there is not what this is about. Signed-off-by: krishhna24 <krishhnatupedev@gmail.com> * Add changelog for #10674 Signed-off-by: krishhna24 <krishhnatupedev@gmail.com> --------- Signed-off-by: krishhna24 <krishhnatupedev@gmail.com>
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.
For a high-level overview of Velero's components, goals, and design process, see ARCHITECTURE.md.
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-users and #velero-dev channel on the Kubernetes Slack server.
Community
Velero is an open community and we welcome your participation. The best way to get involved is to join our bi-weekly community meetings:
- Join the Velero community meetings, held bi-weekly, alternating between Beijing-friendly and US/Europe-friendly time zones.
- Subscribe to the project meeting calendar.
- Chat with us on the Kubernetes Slack
#velero-userschannel and join the mailing list.
See the community page for the full schedule and details.
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.
Governance
Velero's governance describes how the project is run, including the decision-making process, the roles and responsibilities of maintainers, and how to become a maintainer. Governance applies across the Velero org and is maintained at velero-io/.github.
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.18 | 1.18-latest | 1.33.7, 1.34.1, and 1.35.0 |
| 1.17 | 1.18-latest | 1.31.7, 1.32.3, 1.33.1, and 1.34.0 |
| 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 |
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.
Cloud Native Computing Foundation
Velero is a Cloud Native Computing Foundation sandbox project.
Copyright Contributors to Velero, established as Velero a Series of LF Projects, LLC. For website terms of use, trademark policy and other project policies please see https://lfprojects.org/policies/.