Amir Alavi
Amir Alavi
It is certainly in the Work object: ``` spec: suspend: false workload: manifests: - apiVersion: apps/v1 kind: Deployment metadata: annotations: clusterpropagationpolicy.karmada.io/name: duplicate resourcebinding.karmada.io/name: gatekeeper-controller-manager-deployment resourcebinding.karmada.io/namespace: gatekeeper-system resourcetemplate.karmada.io/managed-annotations: clusterpropagationpolicy.karmada.io/name,resourcebinding.karmada.io/name,resourcebinding.karmada.io/namespace,resourcetemplate.karmada.io/managed-annotations,resourcetemplate.karmada.io/managed-labels,resourcetemplate.karmada.io/uid,work.karmada.io/conflict-resolution,work.karmada.io/name,work.karmada.io/namespace resourcetemplate.karmada.io/managed-labels: app.kubernetes.io/managed-by,app.kubernetes.io/name,clusterpropagationpolicy.karmada.io/name,clusterpropagationpolicy.karmada.io/permanent-id,foo.org/duplicate,karmada.io/managed,product,project,resourcebinding.karmada.io/permanent-id,resourcetemplate.karmada.io/retain-replicas,work.karmada.io/permanent-id...
@RainbowMango I believe you need to modify the replicas on the karmada apiserver to reproduce my issue. - modify replicas on karmada-apiserver - observe that member1 replicas are not modified...
thank you @fanhaouu
/ok-to-test would you please squash your commits?
@RomanenkoDenys great feature! would you be open to adding an e2e test for this?
I would be supportive for this but we need to make the corresponding changes in [here](https://github.com/kubernetes/k8s.io/blob/main/registry.k8s.io/images/k8s-staging-descheduler/images.yaml) as well. I'm happy to help with that if others think that we should...
/label tide/merge-method-squash /ok-to-test I can try to get this in 0.30
/label tide/merge-method-squash /ok-to-test /retitle RemovePodsViolatingInterPodAntiAffinity: sort to evict newer pods