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