<p>I have a bunch of pods in a cluster that is almost <em>requesting</em> all (7.35/8) available CPU resources on a node:</p>
<p><a href="https://i.stack.imgur.com/8eQ01.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/8eQ01.png" alt="enter image description here" /></a></p>
<p>even though their actual total <em>usage</em> is almost nothing (0.34/8).</p>
<p>The pod that is currently requesting the most only requests 210m which I guess is not an outrageous amount - also I would like to enforce some sensible minimum request size for all pods in the cluster. Of course that will accumulate when there are lots of pods.</p>
<p>It seems I could easily scale down the request by a factor of 10 and leave the limits where they are to begin with.</p>
<p>But is there something else that I should look into instead before doing that - reducing replica count etc.?</p>
<p>Also it looks a bit strange that the pods are not more evenly distributed between the nodes.</p>
<p><a href="https://i.stack.imgur.com/GQrBF.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/GQrBF.png" alt="enter image description here" /></a></p>

u123
<p>Your request values seems overestimated.
You need time and metrics to find the right request/limit for your workload.</p>
<p>Keep in mind that if you change those values, your pods will restart.</p>
<p>Also, It's normal that you can find some unbalance nodes on your cluster. Kubernetes will never remove a pod if you don't ask.</p>
<p>For example, if your create a cluster with 3 nodes, fill those 3 nodes with pods and then add another 3 nodes. The new nodes will stay empty.</p>
<p>You can setup some <a href="https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/" rel="nofollow noreferrer">HorizontalPodAutoScaler</a> on your cluster to adapt your number of pod to your workload.
Doing that, your workload will spread among nodes and with a correct balance. (if you use the default <a href="https://kubernetes.io/docs/reference/scheduling/policies/" rel="nofollow noreferrer">Scheduling Policy</a></p>
