Make HighNodeUtilization select 1 node if all nodes are underutilized

[zoonage]

Eventually reconcile the issue in #725 by tainting and removing 1 node at a time on each run.

There's definitely a more efficient way by working out how many nodes could be removed to achieve a certain resource utilisation density on the remaining nodes, however this is a quick fix that eventually reconciles the cluster into the desired state

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: zoonage / name: Aaron George (4e73737, cd87f90, d7a1fdd, ddc4fd6)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign damemi for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @zoonage!

It looks like this is your first PR to kubernetes-sigs/descheduler 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/descheduler has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @zoonage. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[zoonage]

This is the first time I've tried to use the de-scheduler, how are the *NodeUtilization plugins preventing pods from being re-scheduled onto the node they've just been evicted from?

[zoonage]

This is the first time I've tried to use the de-scheduler, how are the *NodeUtilization plugins preventing pods from being re-scheduled onto the node they've just been evicted from?

I've added PreferredNoSchedule tainting to nodes now to avoid scheduling on nodes we're trying to remove

[zoonage]

Just realised the tainting has an unintended effect on LowNodeUtilization, will give this a rethink