Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow selecting namespaces to backup on a NS label instead of the NS names #2477

Closed
titou10titou10 opened this issue Apr 29, 2020 · 3 comments
Labels
Enhancement/User End-User Enhancement to Velero Reviewed Q2 2021

Comments

@titou10titou10
Copy link

titou10titou10 commented Apr 29, 2020

velero backup createallows to backup:

  • all resources from namespaces included by their names:--include-namespaces
  • resources that match a certain label :--selector (possibly more restricted by the--include-namespaces above)

What we need is to backup everything belonging to namespaces that have specifically a certain label attached, ie select the namespaces to backup based on an label assigned directly to the namespace, instead of their names

Is there a way to do this?

If not, it would be something like adding a new parameter for this: --include-namespaces-selector?
Thx

@skriss
Copy link
Contributor

skriss commented Apr 29, 2020

@titou10titou10 unfortunately Velero does not currently support this.

We do already have a feature request for this in the backlog - see #503. I'm going to close that one out and leave this one open for tracking.

Are you interested in working on a contribution here? If so, we can discuss more on what the design for this would look like.

@skriss skriss added the Enhancement/User End-User Enhancement to Velero label Apr 29, 2020
@skriss skriss changed the title Hot to select namespaces to backup on a NS label instead of the NS names? Allow selecting namespaces to backup on a NS label instead of the NS names Apr 29, 2020
@bsctl
Copy link

bsctl commented Jun 19, 2020

Having a namespace label selector for all the objects in that namespace, would be a great improvement usage of Velero.

@eleanor-millman
Copy link
Contributor

Closing because will be handled when #2413 is implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement/User End-User Enhancement to Velero Reviewed Q2 2021
Projects
None yet
Development

No branches or pull requests

4 participants