Change node count in a Managed Kubernetes cluster

In Managed Kubernetes clusters, you can change the number of nodes — reduce or increase the number of nodes in a group. For fault-tolerant operation of system components, we recommend using at least two working nodes in a cluster.

When you scale down the number of nodes, random nodes are deleted from the group by default. If necessary, you can delete a specific node. If the group contains one node, you can delete the entire node group. If the Kubernetes version is 1.28 and higher, you can delete all nodes from a node group on a cloud server and leave an empty node group. An empty node group retains node configurations, labels, taints, and user data, but you are not charged for the nodes.

You can change the node group size in the control panel, through the Managed Kubernetes API or through Terraform.

For nodes on dedicated servers, consider their specific payment details. Learn more in the Payment for nodes on dedicated servers when changing the node count.

Payment for nodes on dedicated servers when changing the node count

Payment when increasing the node count

When you increase the number of nodes in a cluster, the payment for the new dedicated servers is deducted as a one-time charge using your primary funds. If there are insufficient primary funds in your balance, the node count will not be increased.

If you need to use bonuses to pay for new nodes on dedicated servers, you can create a new node group and add nodes there.

Refunds when decreasing the node count

When you decrease the number of nodes in a cluster, in accordance with the user agreement, funds for dedicated servers will only be refunded for full unused months.

Change node count

carefully

When you decrease the number of nodes in a cluster, random nodes are deleted from the group by default. You can delete a specific node.

Fixed

1. In the control panel, from the top menu, click Products and select Managed Kubernetes.
2. Open the cluster page → Cluster composition tab.
3. In the node group menu, select Change node count.
4. In the Node count field, open the Fixed tab.
5. Specify the required number of nodes. For fault-tolerant operation of system components, we recommend using at least two worker nodes in the cluster. Nodes can be located in different groups.
6. Click Save.

With autoscaling

For your information

Node group autoscaling is unavailable:

• for node groups with GPU without drivers;
• node groups on dedicated servers.

Autoscaling occurs only if the cluster is in the ACTIVE status.

The actual number of nodes in a group may be less than the minimum number you specify when configuring autoscaling if:

• you increased the minimum node count in the group after creating the group;
• the actual number of nodes is sufficient for the current load, and there is no need to increase the node count.

If a smaller number of nodes is sufficient for the current load in the cluster, but pods cannot be moved for some reason, the node count in the group will not decrease.

Learn more about how autoscaling works in the Autoscaling node groups guide.

1. In the control panel, from the top menu, click Products and select Managed Kubernetes.
2. Open the cluster page → Cluster composition tab.
3. In the node group menu, select Change node count.
4. In the Node count field, open the With autoscaling tab.
5. Set the minimum and maximum number of nodes in the group — the number of nodes will only change within this range. For fault-tolerant operation of system components, we recommend using at least two worker nodes in the cluster. Nodes can be located in different groups.
6. Click Save.

Delete a specific node

You can delete a specific node from a group. After deletion, all pods on this node will be distributed across other nodes in the group.

1. In the control panel, from the top menu, click Products and select Managed Kubernetes.
2. Open the cluster page → Cluster composition tab.
3. In the node menu, select Delete.
4. Enter the node name to confirm deletion.
5. Click Delete.