Change the number of nodes
In Managed Kubernetes clusters you can change the number of nodes — reduce or increase the number of nodes in the group.For fault-tolerant operation of system components, we recommend using at least two working nodes in the cluster.
When you reduce the number of nodes, by default, random nodes in a group are deleted. If necessary, you can delete a specific node.If there is one node in the group, you can delete the entire node group. If the Kubernetes version is 1.28 or higher, in a node group on the cloud server, you can delete all nodes in the group and leave an empty node group. In an empty node group, node configurations, tags, tints and user data are saved, but nodes are not charged.
You can change the size of a node group in the control panel, via API Managed Kubernetes or through Terraform.
For nodes on dedicated servers, please take into account the specifics of their payment. For more details, see Payment for nodes on dedicated servers when changing the number of nodes.
Payment for nodes on dedicated servers when changing the number of nodes
Payment when the number of nodes is increased
When you increase the number of nodes in a cluster, the payment for new dedicated servers is deducted in a one-time payment using fixed assets. If there are not enough fixed assets on the balance used, the number of nodes 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 the number of nodes is reduced
When you reduce the number of nodes in a cluster, as per the user agreement, funds for dedicated servers will only be refunded for full unused months.
Change the number of nodes
When you reduce the number of nodes in a cluster, random nodes in the group are removed by default. You can delete a specific node.
Fixed
With auto scaling
- In the dashboard, on the top menu, click Products and select Managed Kubernetes.
- Open the Cluster page → Cluster Composition tab.
- From the menu of the node group, select Change Number of Nodes.
- In the Number of Nodes field, open the Fixed tab.
- Specify the required number of nodes. For fault-tolerant operation of system components we recommend using at least two working nodes in the cluster, nodes can be in different groups.
- Click Save.
Node group autoscaling is not available:
- for groups of nodes with GPUs without drivers;
- groups of nodes on dedicated servers.
Autoscaling occurs only when the cluster is in ACTIVE
status.
The actual number of nodes in a group may be less than the minimum number you specify when you configure autoscaling if:
- you increased the minimum number of nodes in the group after the group was created;
- the actual number of nodes is sufficient for the existing load and there is no need to increase the number of nodes.
If fewer nodes are sufficient for the current load in the cluster, but the pods cannot be moved for some reason, the number of nodes in the group will not be reduced.
For more information on how autoscaling works, see the Autoscaling node groups instruction.
- In the dashboard, on the top menu, click Products and select Managed Kubernetes.
- Open the Cluster page → Cluster Composition tab.
- From the menu of the node group, select Change Number of Nodes.
- In the Number of nodes field, open the With autoscaling tab.
- Set the minimum and maximum number of nodes in the group — the value of nodes will change only within this range. For fault-tolerant operation of system components we recommend using at least two working nodes in the cluster, nodes can be in different groups.
- Click Save.
Delete a specific node
You can delete a specific node from a group. After deletion, all pods of this node will be distributed to other nodes in the group.
- In the dashboard, on the top menu, click Products and select Managed Kubernetes.
- Open the Cluster page → Cluster Composition tab.
- From the node menu, select Delete.
- Enter the name of the node to confirm the deletion.
- Click Delete.