You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now if there is already a existed workload in member cluster, and the PropagationPolicy matched the workload, karmada will do nothing, because the existed workload (maybe manually created) doesn't have specific karmada labels.
I think we can provide a field to tell karmada if there is a existed workload in member cluster, should it be adopted or just leave it alone.
Why is this needed:
The text was updated successfully, but these errors were encountered:
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/test-infra repository.
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/test-infra repository.
What would you like to be added:
Now if there is already a existed workload in member cluster, and the PropagationPolicy matched the workload, karmada will do nothing, because the existed workload (maybe manually created) doesn't have specific karmada labels.
I think we can provide a field to tell karmada if there is a existed workload in member cluster, should it be adopted or just leave it alone.
Why is this needed:
The text was updated successfully, but these errors were encountered: