From e960ee7f6e77978cfe5909d0ed5ddeb52eed546f Mon Sep 17 00:00:00 2001 From: Stewart-YU Date: Wed, 23 Aug 2017 07:51:29 +0800 Subject: [PATCH] Update out-of-resource.md (#5087) Setting a url. --- docs/tasks/administer-cluster/out-of-resource.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tasks/administer-cluster/out-of-resource.md b/docs/tasks/administer-cluster/out-of-resource.md index 2a4945ad18..a86f70ddf2 100644 --- a/docs/tasks/administer-cluster/out-of-resource.md +++ b/docs/tasks/administer-cluster/out-of-resource.md @@ -377,12 +377,12 @@ to prevent system OOMs, and promote eviction of workloads so cluster state can r ### kubelet may evict more pods than needed The pod eviction may evict more pods than needed due to stats collection timing gap. This can be mitigated by adding -the ability to get root container stats on an on-demand basis (https://github.com/google/cadvisor/issues/1247) in the future. +the ability to get root container stats on an on-demand basis [(https://github.com/google/cadvisor/issues/1247)](https://github.com/google/cadvisor/issues/1247) in the future. ### How kubelet ranks pods for eviction in response to inode exhaustion At this time, it is not possible to know how many inodes were consumed by a particular container. If the `kubelet` observes inode exhaustion, it will evict pods by ranking them by quality of service. The following issue has been opened in cadvisor -to track per container inode consumption (https://github.com/google/cadvisor/issues/1422) which would allow us to rank pods +to track per container inode consumption [(https://github.com/google/cadvisor/issues/1422)](https://github.com/google/cadvisor/issues/1422) which would allow us to rank pods by inode consumption. For example, this would let us identify a container that created large numbers of 0 byte files, and evict that pod over others.