karmada
karmada copied to clipboard
karmada-io
Does karmada can prevent removal of these managed resources
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)
That sounds like a reasonable feature. I'd like to know when and how this feature would be used.
The Kubefed annotation kubefed.io/orphan: true is added to the federated resources, corresponding to Karmada PropagationPolicy. I tend to extend the API instead of introducing an annotation.
I propose a simple idea. Add a new API, call it RemovePolicy, and define the target resource and the corresponding deletion policy in its resources, such as whether to keep the resources in the member cluster, or delete the resources in the member cluster synchronously, how much the deletion delay is, etc.
The idea is very rough, throw bricks lead jade.
That sounds like a reasonable feature. I'd like to know when and how this feature would be used.
Used to migrate some services from karmda. If the services migrated to karmada do not meet expectations, provide a rollback capability.
I propose a simple idea. Add a new API, call it RemovePolicy, and define the target resource and the corresponding deletion policy in its resources, such as whether to keep the resources in the member cluster, or delete the resources in the member cluster synchronously, how much the deletion delay is, etc.
I agreed @RainbowMango idea, Add a new API might be too complicated
Hi everyone, let's use umbrella issue #5577 to track this requirement. /close
@XiShanYongYe-Chang: Closing this issue.
In response to this:
Hi everyone, let's use umbrella issue #5577 to track this requirement. /close
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.
