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
    • Recommended master configurations
    • Audit policy
    • External cluster nodes
    • Quotas and limits
    • Recommendations on using Managed Service for Kubernetes
  • 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 June 5, 2026

You can select the master configuration when creating or updating a cluster. For stable operation, the master configuration must match the cluster workload.

Use the table to select the minimum master configuration based on your cluster parameters. Configurations may change; see the list of available configurations.

The selected configuration sets the minimum resource values for the master. If master autoscaling is enabled in the cluster, the selected configuration is used as the lower scaling boundary.

Cluster parameters

Estimated master requirements

Recommended master configuration

CNI

Nodes

Maximum pods

vCPU

RAM

Standard

CPU Optimized

Memory Optimized

Calico

128

8 192

3 vCPU

12 GB

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

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

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

Calico

128

14 080

6 vCPU

21 GB

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

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

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

Calico

256

16 384

6 vCPU

24 GB

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

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

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

Calico

256

28 160

11 vCPU

42 GB

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

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

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

Calico

512

32 768

12 vCPU

48 GB

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

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

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

Cilium

128

8 192

4 vCPU

16 GB

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

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

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

Cilium

128

14 080

7 vCPU

26 GB

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

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

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

Cilium

256

16 384

8 vCPU

30 GB

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

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

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

Cilium

256

28 160

13 vCPU

51 GB

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

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

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

Cilium

512

32 768

15 vCPU

59 GB

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

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

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

Was the article helpful?

Previous
Autoscaling
Next
Audit policy
© 2026 Direct Cursus Technology L.L.C.