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

Restore empty namespace #2643

Closed
priyansh08 opened this issue Jun 17, 2020 · 1 comment
Closed

Restore empty namespace #2643

priyansh08 opened this issue Jun 17, 2020 · 1 comment

Comments

@priyansh08
Copy link

Describe the problem/challenge you have
A platform operator may have prepared a namespace in a cluster for future workloads.
When they want to migrate the cluster, Velero does not restore an empty namespace, leading to incomplete restoration of the cluster

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

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"
@ashish-amarnath
Copy link
Contributor

There is an existing issue open for this #1970
Closing this one in favor of #1970

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants