-
Notifications
You must be signed in to change notification settings - Fork 891
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
Does karmada can prevent removal of these managed resources #4709
Comments
That sounds like a reasonable feature. I'd like to know when and how this feature would be used. The Kubefed annotation |
I propose a simple idea. Add a new API, call it The idea is very rough, throw bricks lead jade. |
Used to migrate some services from karmda. If the services migrated to karmada do not meet expectations, provide a rollback capability. |
I agreed @RainbowMango idea, Add a new API might be too complicated |
Hi everyone, let's use umbrella issue #5577 to track this requirement. |
@XiShanYongYe-Chang: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What would you like to be added:
Under normal circumstances, delete resource in karmada control plane, resource in mamber cluster will be deleted;
Is there any way to prevent removal of these managed resources?
Why is this needed:
Like kubefed Annotation
kubefed.io/orphan: true
; this feature is useful to rollback when resource migrate to karmada;refer to (https://github.com/kubernetes-retired/kubefed/blob/master/docs/userguide.md)
The text was updated successfully, but these errors were encountered: