-
Notifications
You must be signed in to change notification settings - Fork 450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the kubernetes.kubelet.cpuManagerPolicy
field immutable
#9265
Comments
/assign |
Hi @ialidzhikov, actually we still have the need to change it, make the field immutable would cause some other issue for us. A better way would be, if the worker group's node size is 0, then we can change it, or else we can't. |
What about triggering a rolling update of the nodes when this field is changed? |
Hi @ialidzhikov, if there is any update for this issue? Thanks! |
Sorry, I won't have capacity in the next weeks to look into this issue due to other priorities. /unassign |
In case we would like to pursue the node rolling approach, I assume we have to wait for #9699 first. cc @MichaelEischer @timebertt @kon-angelo - perhaps you want to consider this |
How to categorize this issue?
/area quality
/kind bug
What happened:
With @adenitiu and @nickytd we discovered that changing the
kubernetes.kubelet.cpuManagerPolicy
field breaks kubelet.Afterwards it cannot start successfully with the error logs:
Node events that prove that the kubelet gets constantly restarted:
What you expected to happen:
The
kubernetes.kubelet.cpuManagerPolicy
field to be immutable.How to reproduce it (as minimally and precisely as possible):
Create a worker pool with
kubernetes.kubelet.cpuManagerPolicy=static
.Change the
kubernetes.kubelet.cpuManagerPolicy
field tonone
Make sure that kubelet is failing to start with:
Anything else we need to know?:
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: