Add support for inter-pod affinity strategy about descheduler

[aveshagarwal]

@containscafeine as I explained here: #46 (comment), first I'd suggest to address requiredDuringSchedulingIgnoredDuringExecution.

[ravisantoshgudimetla]

@aveshagarwal - Can you assign appropriate milestone for this? We have pod anti-affinity strategy, do you want to include this in 0.4 release?

[komljen]

I would like to have the ability to set podAffinityType for RemovePodsViolatingInterPodAntiAffinity strategy, similar to nodeAffinityType where we can set required or preffered affinity types. Does this issue covers that scenario?

[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.