MCS leaves orphaned work for endpoitslice sync when ns is deleted

[grosser]

What happened:

I have these work objects leftover after I deleted a namespace that had a MCS
(2 of them since it was going to 2 clusters)

  labels:
    multiclusterservice.karmada.io/name: workload-migration-integration
    multiclusterservice.karmada.io/namespace: workload-migration-integration-mgrosser

What you expected to happen:
work should be deleted

How to reproduce it (as minimally and precisely as possible):

• create ns
• add MCS to ns
• delete ns
• see that work is left over

Anything else we need to know?:

Environment:

• Karmada version: 1.10

[grosser]

might have found a culprit, will reopen if that's not it ...

[grosser]

nope still unclear why this happens

[XiShanYongYe-Chang]

Hi @grosser, thanks for your feedback.

Do you mean to delete the namespace where the MCS object exists? The MCS object will also be deleted at this time?

[grosser]

I deleted the ns which triggered deletion of the MCS object, the issue is that the deletion left behind the work for the endpointslices

[XiShanYongYe-Chang]

Let me try it sometime.