diff options
| author | Rong Gao <gaoronggood@163.com> | 2019-10-30 09:29:54 +0800 |
|---|---|---|
| committer | Rong Gao <gaoronggood@163.com> | 2019-10-30 22:04:37 +0800 |
| commit | e1cb6f1436a67dd01f1858b880d57b62a2667ae0 (patch) | |
| tree | 47c27f3f1cdd043fe0b645ccc85ff42ea132bc09 | |
| parent | ecea14c0af705635a47d6dbc99dc050ed2373065 (diff) | |
change the daemonset specific exception
| -rw-r--r-- | contributors/design-proposals/node/kubelet-eviction.md | 17 |
1 files changed, 4 insertions, 13 deletions
diff --git a/contributors/design-proposals/node/kubelet-eviction.md b/contributors/design-proposals/node/kubelet-eviction.md index 5a61b1ab..51fa9203 100644 --- a/contributors/design-proposals/node/kubelet-eviction.md +++ b/contributors/design-proposals/node/kubelet-eviction.md @@ -456,16 +456,7 @@ placing **any** new pods on the node since they will be rejected by the `kubelet ### DaemonSet -It is never desired for a `kubelet` to evict a pod that was derived from -a `DaemonSet` since the pod will immediately be recreated and rescheduled -back to the same node. - -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. - +As `Priority` is a key factor in the eviction strategy, if you do not want +pods belonging to a `DaemonSet` to be evicted, specify a sufficiently high priorityClass +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.
\ No newline at end of file |