You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 set includeClusterResources 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"
The text was updated successfully, but these errors were encountered:
This is a known issue, but I can't seem to find a related github issue.
I don't think we need to include any new feature gates or configuration, though. I suspect the right answer would be for any backup item action which returns cluster-scoped resources as additional items we need to create a corresponding restore item action which returns those same additional items (which should then be included in the restore as long as the item was in the backup) -- and for those built-in (non-plugin) cases of PVs and CRDs, to make sure those are included in the restore as well (if they are not already).
Describe the problem/challenge you have
I met some challenges when backup a large cluster but try to restore only several namespaces like:
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?
Anything else you would like to add:
Environment:
velero version
): v1.15kubectl version
): v1.31/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.
The text was updated successfully, but these errors were encountered: