Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Managed Service for Kubernetes
  • Comparing with other Yandex Cloud services
  • Getting started
    • Resource relationships
    • Release channels and updates
    • Support for Kubernetes versions
    • Zones of control in Managed Service for Kubernetes
    • Updating node group OS
    • Encryption
    • Networking in Managed Service for Kubernetes
    • Network settings and cluster policies
    • Autoscaling
    • Audit policy
    • External cluster nodes
    • Quotas and limits
    • Recommendations on using Managed Service for Kubernetes
    • Recommended master configurations
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  1. Concepts
  2. Recommended master configurations

Recommended master configurations

Written by
Yandex Cloud
Updated at July 13, 2026
View in Markdown

You can select master configuration when creating or updating your cluster. For stable operation, make sure the master configuration matches the workload of your Kubernetes cluster.

You can use this table to find the minimum master configuration based on your specific cluster specifications. Configurations may change over time. You can view the list of available configurations here.

The selected configuration allocates minimum resources to the master. If you enable master node auto-scaling in your cluster, your selected configuration will serve as the lower scaling limit.

Warning

Starting June 18, 2026, master node auto-scaling will be enabled on all clusters in the RAPID release channel where the master is deployed in a highly available configuration.

Cluster specifications

Estimated master node requirements

Recommended master configuration

CNI

Nodes

Maximum number of pods

vCPU

RAM

Standard

CPU Optimized

Memory Optimized

Calico

128

8 192

3 vCPU

12 GB

4 vCPUs, 16 GB RAM (s-c4-m16)

8 vCPUs, 16 GB RAM (c-c8-m16)

4 vCPUs, 32 GB RAM (m-c4-m32)

Calico

128

14 080

6 vCPU

21 GB

8 vCPUs, 32 GB RAM (s-c8-m32)

16 vCPUs, 32 GB RAM (c-c16-m32)

8 vCPUs, 64 GB RAM (m-c8-m64)

Calico

256

16 384

6 vCPU

24 GB

8 vCPUs, 32 GB RAM (s-c8-m32)

16 vCPUs, 32 GB RAM (c-c16-m32)

8 vCPUs, 64 GB RAM (m-c8-m64)

Calico

256

28 160

11 vCPU

42 GB

16 vCPUs, 64 GB RAM (s-c16-m64)

32 vCPUs, 64 GB RAM (c-c32-m64)

16 vCPUs, 128 GB RAM (m-c16-m128)

Calico

512

32 768

12 vCPU

48 GB

16 vCPUs, 64 GB RAM (s-c16-m64)

32 vCPUs, 64 GB RAM (c-c32-m64)

16 vCPUs, 128 GB RAM (m-c16-m128)

Cilium

128

8 192

4 vCPU

16 GB

4 vCPUs, 16 GB RAM (s-c4-m16)

8 vCPUs, 16 GB RAM (c-c8-m16)

4 vCPUs, 32 GB RAM (m-c4-m32)

Cilium

128

14 080

7 vCPU

26 GB

8 vCPUs, 32 GB RAM (s-c8-m32)

16 vCPUs, 32 GB RAM (c-c16-m32)

8 vCPUs, 64 GB RAM (m-c8-m64)

Cilium

256

16 384

8 vCPU

30 GB

8 vCPUs, 32 GB RAM (s-c8-m32)

16 vCPUs, 32 GB RAM (c-c16-m32)

8 vCPUs, 64 GB RAM (m-c8-m64)

Cilium

256

28 160

13 vCPU

51 GB

16 vCPUs, 64 GB RAM (s-c16-m64)

32 vCPUs, 64 GB RAM (c-c32-m64)

16 vCPUs, 128 GB RAM (m-c16-m128)

Cilium

512

32 768

15 vCPU

59 GB

16 vCPUs, 64 GB RAM (s-c16-m64)

32 vCPUs, 64 GB RAM (c-c32-m64)

16 vCPUs, 128 GB RAM (m-c16-m128)

Was the article helpful?

Previous
Recommendations on using Managed Service for Kubernetes
Next
Access management
© 2026 Direct Cursus Technology L.L.C.