-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Comments
indrajithgihan
changed the title
capability to overwrite existing kubernetes objects
Capability to overwrite existing Kubernetes objects
Apr 21, 2022
There is already an existing PR and issue for this requirement, #4842. |
@indrajithgihan please refer the following:
|
Closing as this will be implemented in v1.9 |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
):1.8.1kubectl version
):1.21.9/etc/os-release
):Ubuntu 18.04.6 LTS / Redhat 7.9Vote 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.
The text was updated successfully, but these errors were encountered: