<p>I am making some tests, and I believe I may be misunderstanding how &quot;allocatable&quot; work.
I have 2 nodes running on Azure-AKS, both with Memory capacity of 65 Gi, and nothing but some basic daemon running on them.
When describing these nodes, I have for both about 59 Gi memory &quot;allocatable&quot;.</p>
<p>Then I start a new pod, with a resources request and limit of 30Gi on one of these node. In practice, the pod use just a couple of Mo.
I would be expecting the &quot;allocatable&quot; to reduce to 29 Gi, but it stays at  59 Gi.</p>
<p>If I am doing a describe, the &quot;allocated&quot; section will correctly display what I actually requested.</p>
<pre><code>Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource                       Requests       Limits
  --------                       --------       ------
   memory                         31190Mi (53%)  32170Mi (55%)
   ....
  
</code></pre>
<p>But not the allocatable:</p>
<pre><code>Allocatable:
  attachable-volumes-azure-disk:  16
  cpu:                            7820m
  ephemeral-storage:              119716326407
  hugepages-1Gi:                  0
  hugepages-2Mi:                  0
  memory:                         59350320Ki
  pods:                           30

</code></pre>
<p><strong>So, is allocatable supposed to take in account the requested resources of the pod ?</strong></p>
<p>If yes, why is the value not decreasing here?</p>
<p>If no, how can I know what is the total amount of request/limit on one specific node (in a parsable format, such as json) ?</p>

Djoby
<p><code>is allocatable supposed to take in account the requested resources of the pod ?</code></p>
<p>No. Allocatable is your underlying instance capacity <strong>minus</strong> all the reserved (eg. system-reserved, kube-reserved, eviction threshold).</p>
<p><code>...how can I know what is the total amount of request/limit on one specific node?</code></p>
<p>You can continue use <code>kubectl describe node</code>, or <code>kubectl top node</code>, or kubernetes dasboard and many other monitoring tools out there.</p>
