Support filter the resource by name during the backup

[ywk253100]

Currently, the --include-resources option of velero backup create command only supports specifying the resource type, but there are requirements that only need to back up a specified resource.

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 "I would like to see this bug fixed as soon as possible"
• 👎 for "There are more important bugs to focus on right now"

[27149chen]

• velero restore for the same requirement

[reasonerjt]

IMO this is a slightly lower priority than #5120
as it feels natural to use label to solve this problem?

[27149chen]

IMO this is a slightly lower priority than #5120 as it feels natural to use label to solve this problem?

I think we should not touch user's resources, and it might cause probelms. Also labels don't work sometimes since resouces owner can revert such changes

[ywk253100]

This issue #5152 describes one option about how to implement this feature

[sseago]

@ywk253100 note that I've suggested a change to #5152 to make it more flexible with respect to includes/excludes as well as less confusing with respect to existing include/exclude behavior.

[neginhsobhani]

Currently, the --include-resources option of velero backup create command only supports specifying the resource type, but there are requirements that only need to back up a specified resource.

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 "I would like to see this bug fixed as soon as possible"
• 👎 for "There are more important bugs to focus on right now"

I've deployed Velero on kubernetes cluster in corporate level and we have the same requirement. Hope they add this feature soon.

[ryankenney-dev]

+1. We are heavily invested in 3rd party helm charts and we often need to exclude resources that cannot be easily tagged (including kube-root-ca.crt). If we could just include/exclude by resource name, this remains maintainable. If not, we are forever playing whac-a-mole to tag the resources in the 3rd party resources... until the day our backups are quietly incomplete.