Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for Kubernetes
  • Comparison with other Yandex Cloud services
  • Getting started
    • Resource relationships
    • Release channels and updates
    • Encryption
      • Cluster autoscaler
      • Evicting pods from nodes
      • Dynamic resource allocation for a node
      • Node groups with GPUs
    • Networking in Managed Service for Kubernetes
    • Network settings and cluster policies
    • Automatic scaling
    • Audit policy
    • External cluster nodes
    • Quotas and limits
    • Managed Service for Kubernetes usage recommendations
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes

In this article:

  • Amount of allocated RAM and CPU resources
  • RAM resource allocation
  • CPU resource allocation
  1. Concepts
  2. Node group
  3. Dynamic resource allocation for a node

Dynamic resource allocation

Written by
Yandex Cloud
Updated at February 14, 2024
  • Amount of allocated RAM and CPU resources
    • RAM resource allocation
    • CPU resource allocation

Nodes need resources to run the Kubernetes components in charge of running the node as part of the Kubernetes cluster. This is why the resulting amount of node resources may not match the resources allocated for the jobs in the Kubernetes cluster.

Some nodes need more resources:

  • Nodes with a more powerful configuration, which can run more containers and more pods, need more resources allocated to them.
  • Nodes running Windows Server. These nodes need more resources than Linux nodes, since they need more resources to support the Windows and Windows Server components that can't run in containers.

To view the node resources allocated to the Kubernetes components, run the command:

kubectl describe node <node_name> | grep Allocatable -B 4 -A 3

Amount of allocated RAM and CPU resources

RAM resource allocation

For RAM, the following resources are allocated:

  • 255 MB of RAM for nodes with less than 1 GB of RAM.
  • 25% from the first 4 GB of RAM.
  • 20% from the next 4 GB of RAM (up to 8 GB).
  • 10% from the next 8 GB of RAM (up to 16 GB).
  • 6% from the next 112 GB (up to 128 GB).
  • 2% from RAM over 128 GB.

100 MB of RAM is additionally reserved on each node for kubelet eviction.

CPU resource allocation

For CPUs, the following resources are allocated:

  • 6% from one core.
  • 1% from the next core (up to two cores).
  • 0.5% from the next two cores (up to four cores).
  • 0.25% from all cores over four.

Was the article helpful?

Previous
Evicting pods from nodes
Next
Node groups with GPUs
© 2025 Direct Cursus Technology L.L.C.