From 45a5a5210f01633c3183630cbf8ec041e2acdb89 Mon Sep 17 00:00:00 2001 From: Jerry Park Date: Thu, 1 Oct 2020 12:57:14 +0900 Subject: [PATCH] Fix issue with tasks/administer-cluster/out-of-resource/ --- content/en/docs/tasks/administer-cluster/out-of-resource.md | 2 +- .../admin/resource}/memory-available.sh | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename content/en/{docs/tasks/administer-cluster => examples/admin/resource}/memory-available.sh (100%) diff --git a/content/en/docs/tasks/administer-cluster/out-of-resource.md b/content/en/docs/tasks/administer-cluster/out-of-resource.md index b989ceac62..973eda947e 100644 --- a/content/en/docs/tasks/administer-cluster/out-of-resource.md +++ b/content/en/docs/tasks/administer-cluster/out-of-resource.md @@ -41,7 +41,7 @@ like `free -m`. This is important because `free -m` does not work in a container, and if users use the [node allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) feature, out of resource decisions are made local to the end user Pod part of the cgroup hierarchy as well as the -root node. This [script](/docs/tasks/administer-cluster/memory-available.sh) +root node. This [script](/examples/admin/resource/memory-available.sh) reproduces the same set of steps that the `kubelet` performs to calculate `memory.available`. The `kubelet` excludes inactive_file (i.e. # of bytes of file-backed memory on inactive LRU list) from its calculation as it assumes that diff --git a/content/en/docs/tasks/administer-cluster/memory-available.sh b/content/en/examples/admin/resource/memory-available.sh similarity index 100% rename from content/en/docs/tasks/administer-cluster/memory-available.sh rename to content/en/examples/admin/resource/memory-available.sh