-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Description
Per email from Jorge Luis Tudela Gonzalez de Riancho
In 3.9 a very helpful note has been added to the DS docs:
Daemonset scheduling is incompatible with project’s default node selector. If you fail to disable it, the daemonset gets restricted by merging with the default node selector. This results in frequent pod recreates on the nodes that got unselected by the merged node selector, which in turn puts unwanted load on the cluster.
Therefore,
- Before you start using daemonsets, disable the default project-wide node selector in your namespace, by setting the namespace annotation openshift.io/node-selector to an empty string:
# oc patch namespace myproject -p \
'{"metadata": {"annotations": {"openshift.io/node-selector": ""}}}'
If you are creating a new project, overwrite the default node selector using
oc adm new-project --node-selector="".
This is valid for 3.7.42 too, I have tested it myself. IMHO it should be included in the 3.7 docs as well.
But I'm not sure if the behaviour in the 3.7.42 is the expected one or not, we better validated that with Engineering before updating the docs.
Cheers.
Thanks!!!
https://docs.openshift.com/container-platform/3.7/dev_guide/daemonsets.html