Lingjun node pools let you manage Lingjun compute nodes in ACK Lingjun managed clusters as a grouped unit — applying container runtime settings, CPU policies, labels, taints, and user-defined data to all nodes in the pool at once, and scheduling workloads to specific nodes or GPU configurations by node pool.
You cannot create Lingjun node pools from the ACK console. To create a node pool, log on to the Intelligent Computing LINGJUN console. For setup instructions, see Create an ACK Lingjun managed cluster.
How it works
Intelligent Computing LINGJUN organizes compute nodes into groups. You can add compute nodes in a cluster to different groups based on your environment, cluster, and compute node requirements to improve the utilization of compute nodes. A Lingjun node pool maps one or more of those LINGJUN groups into a single ACK node pool, so you can manage Lingjun nodes using standard Kubernetes node pool workflows.
Each Lingjun node belongs to exactly one Lingjun node pool.
Features
Lingjun node pools support the same features as ACK node pools. Each node in the pool shares the following configurable attributes:
| Attribute | Description |
|---|---|
| Container runtime | Runtime type and version applied to all nodes |
| CPU management policy | CPU allocation strategy for node workloads |
| Labels and taints | Kubernetes labels and taints for scheduling control |
| User-defined data | Custom metadata attached to nodes |
Default label and taint
Every node in a Lingjun node pool is automatically assigned the following label and taint, which prevent ACK system components from scheduling pods to Lingjun nodes:
| Type | Key | Value / Effect |
|---|---|---|
| Label | alibabacloud.com/lingjun-worker | true |
| Taint | node-role.alibabacloud.com/lingjunEffect | NoSchedule |
To run a pod on a Lingjun node, add a toleration for the taint to the pod spec.
Do not delete the default label or taint. If removed, ACK system components may schedule pods to Lingjun nodes, which can affect your workloads.
