<p>How are Kubernetes Ressource Requests handled in practice, if the "owner" does not use these resources, but another pod would require them? Will they temporarily be granted to the other ressource or do they lead to idle status? </p>

<p>Example: Given two Pods/Deployments (on the same node): </p>

<ul>
<li>Pod A (Requests 40% CPU)  </li>
<li>Pod B (Requests 60% CPU, Limit 80% CPU)</li>
</ul>

<p>Pod A crashes internally, so will never use any ressources (actual usage 0%). 
Questions: </p>

<ol>
<li>Can Pod B Use the 80%, or will it be limited to 60% (to reseve the guaranteed 40% to Pod A, even though Pod A will never use these 40%, effectively leading to 40% Idle Status?)</li>
<li>Could Pod B even getting more than the 80% (on an idle System) or is the 80% absolutely hard enforced? </li>
</ol>

<p>I have not found any docs explaining this in details (they only talk about schedlung based on resources), any links would be very much appreciated...Background/Motivation: I have an extremely slow node app on a pod and I suspect this is realated to Resource Request/Limits... Thanks very much!</p>

Markus
<p>In the node, the only things that kubernetes have is kubelet, kube proxy  and the container runtime wich is responsible to enforce the limits established by kubernetes. So how the limits are enforced depends on wich container runtime you have in kubernetes. Let's suppose your are using Docker. Then get inside your node and check how Docker is establishing limits to your pod.
for example memory limits :
docker inspect   -f "{{.HostConfig.Memory}}" </p>
