Node groups
A Kubernetes node group is a set of worker nodes united under the same name as one collection. Such a group helps you distinguish workloads within a cluster.
This feature does not perform any technical adjustments — it is purely for grouping worker nodes for better management and does not limit interaction between worker nodes from different groups.
Use cases
Some examples of how you can group worker nodes within a cluster:
- Resource segregation — worker nodes with databases in a "High-memory" group, nodes for web services in a "Performance" group
- Environment isolation — "Production" and "Testing" groups
- Temporary resource labeling — a "Temporary" group for resources during peak loads
All clusters created before the feature release are assigned a default group that contains all worker nodes.
Management
Customer Portal
Node groups can be managed in several ways:
- During the cluster order, it is mandatory to create a node group in the Add node modal window.
- When a cluster is active, you can manage groups on the Kubernetes cluster page under the Node groups tab:
- Add node groups
- Delete node groups
- Add nodes to node groups
- You can also move nodes between groups on the Kubernetes cluster page under the Nodes tab.
Public API
Node groups can be managed via the public API using the following requests:
- List node groups for a Kubernetes cluster
- Create a node group for a Kubernetes cluster
- Update a node group for a Kubernetes cluster
- Delete a node group for a Kubernetes cluster
- Move nodes to a group for a Kubernetes cluster
- Update a node for a Kubernetes cluster — to reassign a node to another group
Limitations
- A node group must be associated with a specific cluster and can belong to only one cluster.
- One cluster can have a maximum of 128 node groups.
- Deleting a cluster will delete all associated node groups.
- An empty node group can exist.
- A group containing nodes cannot be deleted.
- Only active nodes can be moved.