You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that change the task name Ensure kube-bench parameters are set in kubernetes/preinstall/tasks/0080-system-configurations.yml into Ensure kubelet expected parameters are set
Because those kernel parameters' values are expected for kubelet to be set before kubelet service start (if --protect-kernel-default=false then kubelet will set those parameters).
As you can see above kubelet related codes, kubelet will validate and set (if needed) the kernel parameters.
Why is this needed
These kernel parameters are the expected values for kubelet to operate, so it would be good to change the task name for a clearer understanding of its operation.
The text was updated successfully, but these errors were encountered:
What would you like to be added
I think that change the task name
Ensure kube-bench parameters are set
inkubernetes/preinstall/tasks/0080-system-configurations.yml
intoEnsure kubelet expected parameters are set
kubespray/roles/kubernetes/preinstall/tasks/0080-system-configurations.yml
Lines 107 to 121 in e013558
Because those kernel parameters' values are expected for kubelet to be set before kubelet service start (if
--protect-kernel-default=false
then kubelet will set those parameters).https://github.com/kubernetes/kubernetes/blob/1dc30bf90fd6a729d226b4e942118110b0a73e65/pkg/kubelet/cm/container_manager_linux.go#L400-L446
https://github.com/kubernetes/kubernetes/blob/1dc30bf90fd6a729d226b4e942118110b0a73e65/staging/src/k8s.io/component-helpers/node/util/sysctl/sysctl.go#L26-L65
As you can see above kubelet related codes, kubelet will validate and set (if needed) the kernel parameters.
Why is this needed
These kernel parameters are the expected values for kubelet to operate, so it would be good to change the task name for a clearer understanding of its operation.
The text was updated successfully, but these errors were encountered: