Open
Description
Describe the problem/challenge you have
I met some challenges when backup a large cluster but try to restore only several namespaces like:
- Additional items added by backup actions, like clusterroles, will not restored automatically.
- Cannot choose the specified cluster-scoped resources to restore as
includedClusterScopedResources
in Backup. And setincludeClusterResources
true may bring unexpected resources.
I think this may because, backup should include resources as much as possible to ensure the applications can run well after migration. But if add additional items in restore should be carefully designed.
Describe the solution you'd like
Is there any solution for such cases?
- Maybe some related actions can be used in restore to add additional items. And these actions can be optional by flag or feature-gate.
- Support the new filters in restore to only include the cluster-scoped resources in need.
Anything else you would like to add:
Environment:
- Velero version (use
velero version
): v1.15 - Kubernetes version (use
kubectl version
): v1.31 - Kubernetes installer & version: ACK
- Cloud provider or hardware configuration: Alibaba Cloud
- OS (e.g. from
/etc/os-release
):
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
- 👍 for "The project would be better with this feature added"
- 👎 for "This feature will not enhance the project in a meaningful way"