<p><strong>Use case / Problem</strong></p>

<p>I am in charge of maintaining a kubernetes cluster with 40 nodes (split across 2 zones). We have roughly 100 microservices and platform stuff like Kafka brokers running in this cluster. All microservices have defined resource request &amp; limits. Most of them however are burstable and don't have guaranteed RAM. Developers who deploy their services in our cluster defined limits far greater than the request (see example below) which eventually caused a lot of evicted pods on various nodes.  We still want to use burstable resources in our services though, as we can save money using burstable resources. Therefore I need a better monitoring possibility of all pods running on each node, containing these information:</p>

<ul>
<li>Node name &amp; CPU / RAM capacity</li>
<li>All pod names plus

<ul>
<li>pod's resource requests &amp; limits</li>
<li>pod's current cpu &amp; ram usage</li>
</ul></li>
</ul>

<p>This way I could easily identify two problematic kind of services:</p>

<p><strong>Case A:</strong> The microservice which just sets huge resource limits, because the developer was just testing stuff or is too lazy to bench/monitor his service</p>

<pre><code>resources:
  requests:
    cpu: 100m
    ram: 500Mi
  limits:
    cpu: 6
    ram: 20Gi
</code></pre>

<p><strong>Case B:</strong> Too many services on the same node which have set not accurate resource limits (e. g. 500Mi, but the service constantly uses 1.5Gi RAM). This case happened to us, because Java developers didn't notice the Java garbage collector will only start to cleanup when 75% of the available RAM has been used.</p>

<p><strong>My question:</strong></p>

<p>How could I properly monitor this and therefore identify misconfigured microservices in order to prevent such eviction problems? At a smaller scale I could simply run <code>kubectl describe nodes</code> and <code>kubectl top pods</code> to figure it out manually, but at this scale that doesn't work anymore.</p>

<p><em>Note:</em> I couldn't find any existing solution for this problem (including prometheus + grafana boards using kube metrics and similiar). I thought it's possible but visualizing this stuff in Grafana is really hard.</p>

<p>This is a known issue as there is still an open <a href="https://github.com/kubernetes/kubernetes/issues/17512" rel="nofollow noreferrer">github issue</a> and the community is requesting developers to create a new command which would show pod/container total CPU and memory usage. Please check this link as there are some ideas and workarounds provided by the community which look like they could be useful for your case. </p>

<p>Did you use proper metrics and you were not able to see the required information? 
<a href="https://github.com/kubernetes/kube-state-metrics/blob/master/Documentation/pod-metrics.md" rel="nofollow noreferrer">Here</a> is a list of pod metrics and I think some of them would be useful for your use case. </p>

<p>Even though there is no fully functional solution to this issue thanks to the community and some other resources there are a couple ways of achieving your goal:
As advised in this <a href="https://dzone.com/articles/kubernetes-resource-usage-how-do-you-manage-and-mo" rel="nofollow noreferrer">article</a>:</p>

<pre><code>kubectl get nodes --no-headers | awk '{print $1}' | xargs -I {} sh -c 'echo {}; kubectl describe node {} | grep Allocated -A 5 | grep -ve Event -ve Allocated -ve percent -ve -- ; echo'
</code></pre>

<p>Also the author of this article recommends <a href="https://www.coscale.com/" rel="nofollow noreferrer">CoScale</a> I haven't used it but it seems it is worth a try if other solutions fail. </p>

<p>I think that another point is that you might never be in control if your developers keep allocating far greater resources than it is needed. Solution recommended by <a href="https://stackoverflow.com/users/2718151/nicola-ben">Nicola Ben</a> would help you mitigate issues like this. </p>
