[Release-1.32] - Kubelet read-only-port is not set to 0 on k3s 1.32+

[brandond]

Backport fix for Kubelet read-only-port is not set to 0 on k3s 1.32+

• Kubelet read-only-port is not set to 0 on k3s 1.32+ #12164

[VestigeJ]

Previous release behavior visible in the return from the configz raw api

$ k3s -v

k3s version v1.32.3+k3s1 (079ffa8d)
go version go1.23.6

$ kg --raw "/api/v1/nodes/ip-1-1-1-25/proxy/configz" | grep -i readonlyport
// output is truncated

"kubeletconfig":{"enableServer":true,"staticPodPath":"/var/lib/rancher/k3s/agent/pod-manifests","podLogsDir":"/var/log/pods","syncFrequency":"1m0s","fileCheckFrequency":"20s","httpCheckFrequency":"20s","address":"0.0.0.0","port":10250,"readOnlyPort":10255,

The current v1.32.4-rc1+k3s1 doesn't have the variable passed into the config on startup and it is correctly absent from the output.

$ kg --raw "/api/v1/nodes/ip-1-1-1-14/proxy/configz" | grep -i readonlyport

Same server version but explicitly passing the value during installation

$ kg --raw "/api/v1/nodes/ip-1-1-1-14/proxy/configz" | grep -i readonlyport

// truncated output

"readOnlyPort":10111

$ k3s -v

k3s version v1.32.4-rc1+k3s1 (6b330558)
go version go1.23.6