Tiger KaovilaiandGitHub
7d88457591
* Design: namespace selection by label in resource policy Extends includeExcludePolicy in the ResourcePolicy ConfigMap with includedNamespacesByLabel and excludedNamespacesByLabel, letting users dynamically include/exclude namespaces by Kubernetes label selector without touching BackupSpec or schedule specs. Covers precedence rules against BackupSpec.IncludedNamespaces/ ExcludedNamespaces (including the empty-IncludedNamespaces "all namespaces" baseline and a configured selector matching zero namespaces), observability via logging (backup.status.includedNamespaces is deferred, see Open Issues), and rejected alternatives (extending BackupSpec.LabelSelector, a new CRD field, a standalone ConfigMap, matching the fine-grained filters' map[string]string selector shape). resolveNamespacesByLabel resolves included/excluded selectors independently and returns both sets uncombined; the caller merges them against BackupSpec.IncludedNamespaces/ExcludedNamespaces via an explicit labelIncludeActive flag, so exclude-only policies and zero-match include selectors both behave correctly instead of collapsing to "all namespaces". Cross-checked against the fine-grained backup/restore filter policies merged from issue #9448 (clusterScopedFilterPolicy, namespacedFilterPolicies in internal/resourcepolicies/resource_policies.go): confirms no field/key collisions, documents that a ConfigMap using these fields can't be reused for Restore (ValidateForRestore rejects any non-nil IncludeExcludePolicy) or the global backup volume policies ConfigMap (volumePolicies-only). Fixes #9771 > [!Note] > Responses generated with Claude Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com> * Design: address review feedback from adam-jian-zhang - Add markdown hard-line-break trailing spaces to Glossary entries so each term renders on its own line. - Add labelSelectorLogic ("OR" default | "AND") to IncludeExcludePolicy instead of deferring AND-vs-OR to a future enhancement, per review comment. AND combines entries within includedNamespacesByLabel (and independently within excludedNamespacesByLabel) via intersection instead of union. Threaded through resolveNamespacesByLabel, validation, and a new worked example. - Change observability logging from "log the full resolved namespace list at info" to "log the count at info, full list at debug" to avoid spamming backup logs on clusters with large namespace counts where a selector matches a large fraction of them. > [!Note] > Responses generated with Claude Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com> * Design: clarify LabelSelector interaction with label-resolved namespaces Non-Goals previously asserted BackupSpec.LabelSelector/OrLabelSelectors are unaffected by this design without qualification. Add the missing trade-off: a namespace resolved into the effective set via includedNamespacesByLabel still gets its Namespace object written even if it doesn't separately match LabelSelector/OrLabelSelectors, mirroring existing behavior for namespaces named explicitly in BackupSpec.IncludedNamespaces (the nsTracker guard in pkg/backup/item_collector.go only suppresses the Namespace object when the namespace filter is at its default, per #7105). Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com> --------- Signed-off-by: Tiger Kaovilai <tkaovila@redhat.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.
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/.