What happened?

The system_reserved variable is described as “Optionally reserve resources for OS system daemons.”

Prior to version 2.27, setting system_reserved: false (the default) caused the systemReserved section to be omitted from kubelet-config.yml.

Since version 2.27 (see commit 1bc61c9), the systemReserved section is always created, regardless of the value of system_reserved.

What did you expect to happen?

I expected the behavior to remain unchanged, or for the change to be documented.

How can we reproduce it (as minimally and precisely as possible)?

1. Deploy a cluster with default settings (system_reserved: false).
2. Inspect kubelet-config.yml.
3. Observe that the systemReserved section is present, even though system_reserved is disabled.

OS

Oracle Linux 8

Version of Ansible

ansible [core 2.16.14]
config file = /home/user/kubespray/ansible.cfg
configured module search path = ['/home/user/kubespray/library']
ansible python module location = /home/user/kubespray/venv/lib/python3.10/site-packages/ansible
ansible collection location = /home/user/.ansible/collections:/usr/share/ansible/collections
executable location = /home/user/kubespray/venv/bin/ansible
python version = 3.10.12 (main, May 27 2025, 17:12:29) [GCC 11.4.0] (/home/user/kubespray/venv/bin/python3)
jinja version = 3.1.4
libyaml = True

Version of Python

Python 3.10.12

Version of Kubespray (commit)

45140b5

Network plugin used

calico

Full inventory with variables

Not relevant

Command used to invoke ansible

Not relevant

Output of ansible run

Not relevant

Anything else we need to know

No response