taint node with PreferNoSchedule until it gets drained

[damoon]

In case of multiple nodes asking to restart, pods will be moved more often then needed, because they can start on the node that will be rebooted next.
The use of PreferNoSchedule on nodes waiting to be rebooted, will prefer scheduling pods onto already rebooted nodes.

link: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/

[github-actions]

This issue was automatically considered stale due to lack of activity. Please update it and/or join our slack channels to promote it, before it automatically closes (in 7 days).

[damoon]

@weaveworksbot i am still interested in this

[bboreham]

Isn't there a danger that every node is waiting to reboot (e.g. if Ubuntu push out a security patch), so this would mean no pods can get scheduled?

[damoon]

The taint is PreferNoSchedule not NoSchedule.
The scheduler will try to avoid putting pods on these nodes, but do it if no other placement is possible.