confusing with "RemovePodsViolatingInterPodAntiAffinity" strategy about descheduler

[ravisantoshgudimetla]

/assign

[ravisantoshgudimetla]

@wjiangjay Are you still seeing the issue? If yes, can you increase debug level and provide logs?

[afoninsky]

I'm confused too. Either I did not understand core concept, or I failed with configs.

I expect pods will be rescheduled with following configuration rules, but they are not:

❯ kubectl -n fulldive-staging get pod -l app=fulldive-api -o wide                                                         kubernetes/git/NAME                          READY     STATUS    RESTARTS   AGE       IP          NODE
fulldive-api-c97f775c-lgtrl   2/2       Running   0          2h        10.48.8.7   gke-staging-default-pool-1ec08eb0-7xkq
fulldive-api-c97f775c-nwrcj   2/2       Running   0          2h        10.48.8.5   gke-staging-default-pool-1ec08eb0-7xkq
fulldive-api-c97f775c-z6z6n   2/2       Running   0          2h        10.48.8.6   gke-staging-default-pool-1ec08eb0-7xkq

      affinity:
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 5
            podAffinityTerm:
              topologyKey: "kubernetes.io/hostname"
              labelSelector:
                matchLabels:
                  app: fulldive-api

    apiVersion: descheduler/v1alpha1
    kind: DeschedulerPolicy
    strategies:
      RemovePodsViolatingInterPodAntiAffinity:
        enabled: true

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

[abessifi]

@wjiangjay Are you still seeing the issue? If yes, can you increase debug level and provide logs?

It's not clear for me how to setup log level:

-v, --v Level log level for V logs

Any help on this please ?