Node configurations in a Managed Kubernetes cluster
In a Managed Kubernetes cluster, you can use cloud server configurations and dedicated server configurations to create node groups.
You can view configuration availability by location in the Managed Kubernetes subsection of the Product Availability by Location guide.
When choosing a configuration, keep in mind that some resources are reserved for system components, so the amount of resources available for pod placement differs from the amount specified in the configuration.
Node configurations on the cloud server
There are three types of configurations available for cloud server nodes:
- custom configurations — you can specify any resource ratio;
- fixed configurations with GPU — ready-to-use node configurations with graphics processors, where the resource ratio is fixed;
- fixed cloud server configurations — cloud server configurations (flavors) with a fixed resource ratio. They can only be added via the Managed Kubernetes API or Terraform.
You can compare available configurations in the Comparing Node Configurations on Cloud Server table.
If the available configurations do not suit your needs, for example, if you need more vCPU or RAM, create a ticket and we will find configurations with a different amount of resources for you.
Custom configurations
In custom node configurations, you can specify the required number of resources. The limits depend on the pool; you can view them in the Comparing Node Configurations on Cloud Server table.
As a boot disk for nodes, you can select a local disk or one of the types of network volumes.
When choosing a configuration with a network volume, keep in mind that changing the IOPS limit is not supported for SSD Universal v2 and SSD Rapid v2 network volumes.
A fault-tolerant multizonal cluster uses cloud servers with dedicated cores and applies Hyper-Threading technology. In this cluster type, you can only select an even number of vCPUs.
Fixed configurations with GPU
You can select a fixed configuration with dedicated GPUs and a specified resource ratio. The configurations correspond to the GPU line of cloud servers.
Detailed characteristics of graphics processors can be found in the Available GPUs subsection of the Create a Managed Kubernetes Cluster with GPU guide.
As a boot disk for nodes, you can select a local disk or one of the types of network volumes. You can select the size for a network volume, while the size for a local disk is fixed.
When selecting a configuration, keep in mind that:
- for network volumes of the SSD Universal v2 and SSD High-Speed v2 types, changing the IOPS limit is not supported;
- some fixed configurations with GPU only have a local disk available.
Fixed cloud server configurations
Fixed cloud server configurations are only available via the Managed Kubernetes API or Terraform.
If the Managed Kubernetes configurations in the Control Panel do not meet your needs, you can use fixed cloud server configurations (flavors). Available flavors can be viewed in the List of Flavors for Cloud Server Lines guide.
In a fault-tolerant multizonal cluster, only the Standard and HighFreq lines with dedicated cores are available.
Comparison of node configurations on the cloud server
Managed Kubernetes configurations
Fixed cloud server configurations
* If the configuration has more than 8 vCPUs, you can select RAM with a ratio of at least 1:2. For example, if you have selected 10 vCPUs, the RAM must be at least 20 GB.
** If the configuration has more than 8 vCPUs, you can select the local disk size with a ratio of at least 1:32. For example, for 10 vCPUs, the minimum disk size is 320 GB.
You can view configuration availability by location in the Managed Kubernetes and GPU for Managed Kubernetes subsections of the Product Availability by Location guide.
Dedicated server node configurations
In Managed Kubernetes clusters, you can create nodes on dedicated servers of prebuilt configurations. The servers must meet the following requirements:
- has a local port;
- x86 processor.
You can view detailed information about configurations in the configurator.
Dedicated servers are assembled and mounted in racks in advance, so they are ready for use within one hour after creating a cluster or node group (excluding the time required for OS installation).