whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

change the daemonset specific exception (#17242)

Browse Source
This commit is contained in:
Rong Gao
2019-11-02 14:21:40 +08:00
committed by Kubernetes Prow Robot
parent 3aab039ac4
commit 851cd9e774
1 changed files with 4 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/administer-cluster/out-of-resource.md
+4 -10
View File
@@ -329,17 +329,11 @@ and trigger eviction assuming those Pods use less than their configured request.
### DaemonSet ### DaemonSet
It is never desired for `kubelet` to evict a `DaemonSet` Pod, since the Pod is As `Priority` is a key factor in the eviction strategy, if you do not want
immediately recreated and rescheduled back to the same node. 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.
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 is strongly recommended that `DaemonSet` not
create `BestEffort` Pods to avoid being identified as a candidate Pod
for eviction. Instead `DaemonSet` should ideally launch `Guaranteed` Pods.
## Deprecation of existing feature flags to reclaim disk ## Deprecation of existing feature flags to reclaim disk