Kubelet Fails to Start When 'reserved-cpus' Argument Does Not Match Node's CPU Topology
This document (000021002) is provided subject to the disclaimer at the end of this document.
Situation
Kubelet Fails to Start When 'reserved-cpus' Argument Does Not Match Node's CPU Topology
Resolution
The explicit reserved CPU option (-- reserved-cpus) defines the explicit cpuset for the System/Kubernetes daemons, as well as the interrupts and timers. The kubelet's reserved-cpus flag value should be compatible with the node's CPU configuration. e.g., if you set reserved-cpus to 3 where a node has only 2 CPUs, then kubelet will fail to start with the following error message:
E0627 07:42:17.202998 2496078 server.go:302] "Failed to run kubelet" err="failed to run Kubelet: reserved-cpus: 3 is not a subset of online-cpus: 0-1"
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000021002
- Creation Date: 04-Mar-2023
- Modified Date:29-Aug-2025
-
- SUSE Rancher
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
