Help Center/
Cloud Container Engine/
Drawer/
Configuration Reference/
Nodes/
kubelet/
Topology Manager Policy
Updated on 2025-06-13 GMT+08:00
Topology Manager Policy
It controls the topology management policy which improves container performance. Options:
- none: This is the default policy and does not perform any topology alignment.
- best-effort: With this policy, kubelet attempts to allocate CPUs and devices on NUMA nodes to a pod as best as it can.
- restricted: With this policy, kubelet allocates CPUs and devices on NUMA nodes only to a pod. If there are no requested resources on the NUMA nodes, Topology Manager will reject this pod from the nodes.
- single-numa-node: With this policy, kubelet only allocates CPUs and devices on exactly one NUMA node to a pod. If there are no requested resources on the NUMA node, Topology Manager will reject this pod from the node.
Value Range
none, best-effort, restricted, or single-numa-node
Default Value
none
Modifiable
Yes
Scope
CCE standard and CCE Turbo clusters
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot