Support cluster resource Includes/Excludes in restore flow

[anshulahuja98]

Describe the problem/challenge you have

Include/Exclude clusterscope/namespace scope filtering was added for backup/schedule flow as part of following issue and PR.

#5120
#5838

There should a parity of this filtering on the restore side as well.

Describe the solution you'd like

Include/exclude cluster scope/namespace scope resource filtering support in restore contracts.

Anything else you would like to add:

Environment:

• Velero version (use velero version):
• Kubernetes version (use kubectl version):
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
• 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"

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue was closed because it has been stalled for 14 days with no activity.

[github-actions]

This issue was closed because it has been stalled for 14 days with no activity.

[anshulahuja98]

/not stale

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[anshulahuja98]

/not stale

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[anshulahuja98]

/not stale

[blackpiglet]

@anshulahuja98
Is there any scenario that needs this feature?
If there is, we can prioritize this issue, and check whether this one should be put into v1.14 scope.

[anshulahuja98]

no prioritization from my end, it is more of a backlog item for feature parity.

[reasonerjt]

Given there's no specific use case, let me put this in backlog for now. We can revisit when the real use cases emerge.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue was closed because it has been stalled for 14 days with no activity.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.