kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

change the daemonset specific exception

This commit is contained in:
Rong Gao 2019-10-30 09:29:54 +08:00
parent ecea14c0af
commit e1cb6f1436
1 changed files with 4 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
contributors/design-proposals/node/kubelet-eviction.md
View File

@ -456,16 +456,7 @@ placing **any** new pods on the node since they will be rejected by the `kubelet
### DaemonSet ### DaemonSet
It is never desired for a `kubelet` to evict a pod that was derived from As `Priority` is a key factor in the eviction strategy, if you do not want
a `DaemonSet` since the pod will immediately be recreated and rescheduled pods belonging to a `DaemonSet` to be evicted, specify a sufficiently high priorityClass
back to the same node. in the pod spec template. If you want pods belonging to a `DaemonSet` to run only if
there are sufficient resources, specify a lower or default priorityClass.
At the moment, the `kubelet` has no ability to distinguish a pod created
from `DaemonSet` versus any other object. If/when that information is
available, the `kubelet` could pro-actively filter those pods from the
candidate set of pods provided to the eviction strategy.
In general, it should be strongly recommended that `DaemonSet` not
create `BestEffort` pods to avoid being identified as a candidate pod
for eviction. Instead `DaemonSet` should ideally include Guaranteed pods only.