<p>For better understand my doubts, I will put an example</p>
<p>Example:</p>
<p>We have one worker node with 3 allocatable cpus and kubernetes has scheduled three pods on it:</p>
<ul>
<li>pod_1 with 500m cpu request</li>
<li>pod_2 with 700m cpu request</li>
<li>pod_3 with 300m cpu request</li>
</ul>
<p>In this worker node I can't schedule other pods.</p>
<p>But if I check the real usage:</p>
<ul>
<li>pod_1 cpu usage is 300m</li>
<li>pod_2: cpu usage is 600m</li>
</ul>
<p>My question is:</p>
<p>Can pod_3 have a real usage of 500m or the request of other pods will limit the cpu usage?</p>
<p>Thanks</p>
<p>Pietro</p>

P3pp3r
<p>It doesn't matter what the real usage is - the &quot;request&quot; means how much resources are guaranteed to be available for the pod. Your workload might be using only a fraction of the requested resources - but what will really count is the &quot;request&quot; itself.</p>
<p>Example - Let's say you have a node with 1CPU core.</p>
<p><strong>Pod A</strong> - 100m Request</p>
<p><strong>Pod B</strong> - 200m Request</p>
<p><strong>Pod C</strong> - 700m Request</p>
<p>Now, no pod can be allocated in the node  - because the whole 1 CPU resource is already requested by 3 pods. It doesn't really matter which fraction of the allocated resources each pod is using at any given time.</p>
<hr />
<p>Another point worth noting is the &quot;Limit&quot;. A requested resource usage could be surpassed by a workload - but it cannot surpass the &quot;Limit&quot;. This is a very important mechanism to be understood.</p>
