# Scheduling not balanced

**URL:** <https://discuss.kubernetes.io/t/scheduling-not-balanced/18210>\
**Category:** General Discussions\
**Created:** [November 24, 2021, 6:58am UTC](https://discuss.kubernetes.io/t/scheduling-not-balanced/18210 "2021-11-24T06:58:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tcheronneau](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/tcheronneau/32/9009_2.png) [@tcheronneau](https://discuss.kubernetes.io/u/tcheronneau)\
**Post date:** [November 24, 2021, 6:58am UTC](https://discuss.kubernetes.io/t/scheduling-not-balanced/18210/1 "2021-11-24T06:58:37Z")

</div>

Asking for help? Comment out what you need so we can get more information to help you!

### Cluster information:

Kubernetes version: 1.20.11  
Cloud being used: (put bare-metal if not on a public cloud) bare-metal  
Installation method: kubeadm  
Host OS: RedHat  
CNI and version: calico 3.17.3  
CRI and version: containerd 1.4.7

You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.

We have a weird behavior of the scheduler in our cluster.  
Our cluster is composed of 4 worker nodes.  
Currently we often have one node which is more loaded than the others so sometime I’m trying to reschedule workload to spread it elsewhere but most of the time it does not work (stays on the heavier node).  
Even worse when creating new workload most of the time the scheduler launch it on this most used node.  
We tried to start from scratch our load but it always end like that.  
I don’t see anything in our cluster that could cause this bad behavior.  
We don’t use priority class nor affinity nor selector for nodes.

If someone has some input that can help it would be much appreciate.

Thanks,  
Thomas.