Kubernetes Node Memory Limits


I'm a beginner on Kubernetes. When I described my node, I saw this at the very bottom:

kubectl describe node ip-x-x-x-x.ap-southeast-2.compute.internal 


Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
CPU Requests  CPU Limits  Memory Requests  Memory Limits
------------  ----------  ---------------  -------------
225m (11%)    200m (10%)  125Mi (1%)       300Mi (3%)
Events:         <none>

How do I un-limit the memory + cpu?

-- krisanalfa

1 Answer


Every node has limits according to its resources: number of processors or cores, amount of memory. Kubernetes uses this information for distributing Pods across Nodes.

Referring to the official documentation:

- Meaning of CPU
One CPU, in Kubernetes, is equivalent to:
- 1 AWS vCPU
- 1 GCP Core
- 1 Azure vCore
- 1 Hyperthread on a bare-metal Intel processor with Hyperthreading
1 CPU is 1000m (1 thousand milicores)

- Meaning of memory. It is an amount of memory on the server.

In the output from kubectl describe node <node-name> command, you see statistics of resource usage. Actually, resources of your server can be counted from the example in question, it is 2 CPUs/Cores and around 10000 MB of memory.

Please note that some resources are already allocated by system Pods like kube-dns, kube-proxy or kubernetes-dashboard.

-- Artem Golenyaev
Source: StackOverflow