Amir Alavi

Code path that enforces one per kind/operation: https://github.com/karmada-io/karmada/blob/master/pkg/webhook/resourceinterpretercustomization/helper.go#L29C67-L46

That is what we ended up doing (putting everything in one and using conditional statement), but as mentioned in the Issue, it would be nice to split it up to...

>What's the pain point for now? In the example given in the Issue, we have to add bunch of conditional statements to switch based on secret type to retain respective...

Created a PR to get feedback: https://github.com/karmada-io/karmada/pull/4689

>May I ask for more detailed info about how you do the migration? I don't understand how can the workload be synced from blue to green, I understand both the...

@XiShanYongYe-Chang I have updated the PR to reflect the requested changes. I look forward to your feedback

>Can you elaborate on this step a little bit? Given that we have two clusters: 1. cluster-blue: this is where the original workloads are (and karmada controller-manager also runs here...

No, given that we still rely on karmada-controller-manager for handling propagation syncs. After step 9, however, it needs to be suspended. I think this feature request is generic enough to...

There are other resources such as Secrets, ServiceAccount as well. I tried creating this PR here: https://github.com/karmada-io/karmada/pull/4620 but `karmada.io/managed: true` applies to all "normal" workload propagation as well. So we...

Hi @XiShanYongYe-Chang I am only interested in ones "created by the Karmada system". As far as ones "propagated by users through Karmada", we have other labels that we could use...