Configure Node Resource Reservation
Use a KubeletConfig object to reserve CPU, memory, and ephemeral storage for the operating system and Kubernetes components. Machine Configuration applies the reservation to nodes that run Alauda OS.
TOC
Supported FieldsUse Automatic ReservationSet Static Reservation ValuesVerify the ReservationLimitationsSupported Fields
This API does not manage other kubelet settings.
Use Automatic Reservation
Machine Configuration creates acp-default-node-reservation on supported clusters. It calculates systemReserved on each node. Do not set systemReserved in an automatic reservation object.
The default control plane and worker pools have the machineconfiguration.alauda.io/node-reservation=true label.
Set Static Reservation Values
Use static mode when every selected node must use the same values.
-
Create the target worker pool and assign nodes to it. See Managing Node Configuration. This example uses a pool named
worker-static. -
Label the pool:
-
Apply a static
KubeletConfig:
Static mode uses only the values in spec.kubeletConfig.
Verify the Reservation
-
Check the reservation object:
For static mode, replace the name with
worker-static-reservation. -
Check the node state:
STATEshould beDone, andCURRENTshould matchDESIRED. -
On a target node, check the kubelet arguments:
For automatic mode, also check the calculated result:
The result should include
--system-reserved. If the file contains onlyACP_KUBELET_STATIC_ARGS, the calculation has not finished.
A successful update restarts kubelet. It does not plan a node reboot.
Limitations
- The feature applies only to supported clusters that run Alauda OS and Machine Configuration.
- Automatic mode calculates
systemReservedonly. - A node pool can match only one
KubeletConfig.