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

Capability to overwrite existing Kubernetes objects #4851

Closed
indrajithgihan opened this issue Apr 21, 2022 · 3 comments
Closed

Capability to overwrite existing Kubernetes objects #4851

indrajithgihan opened this issue Apr 21, 2022 · 3 comments

Comments

@indrajithgihan
Copy link

Describe the problem/challenge you have

Currently If some resource already exists and differs from one in the backup, Velero will not overwrite it. Velero doesn't overwrite objects in-cluster if they already exist.

Describe the solution you'd like

Please provide Velero tool the capability to overwrite Kubernetes objects if they already exist

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

Environment:

  • Velero version (use velero version):1.8.1
  • Kubernetes version (use kubectl version):1.21.9
  • Kubernetes installer & version: kubeadm 1.21.9
  • Cloud provider or hardware configuration: On-prem and AKS
  • OS (e.g. from /etc/os-release):Ubuntu 18.04.6 LTS / Redhat 7.9

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"
@indrajithgihan indrajithgihan changed the title capability to overwrite existing kubernetes objects Capability to overwrite existing Kubernetes objects Apr 21, 2022
@Lyndon-Li
Copy link
Contributor

There is already an existing PR and issue for this requirement, #4842.
Please review it and check whether it meets your requirement.

@shubham-pampattiwar
Copy link
Collaborator

@indrajithgihan please refer the following:

@reasonerjt
Copy link
Contributor

Closing as this will be implemented in v1.9

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

4 participants