From b5a09f68deb473c2acb277adb1aaa54616eb94f1 Mon Sep 17 00:00:00 2001 From: Cliff Burdick <30670611+cliffburdick@users.noreply.github.com> Date: Sun, 18 Nov 2018 18:38:22 -0800 Subject: [PATCH] Fixing yaml (#10541) The current YAML doesn't work since hugepages requires you to include memory and/or CPU limits as well, or you get the error: "HugePages require cpu or memory". --- .../en/docs/tasks/manage-hugepages/scheduling-hugepages.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/en/docs/tasks/manage-hugepages/scheduling-hugepages.md b/content/en/docs/tasks/manage-hugepages/scheduling-hugepages.md index e8bb5ef319..82b3c34d27 100644 --- a/content/en/docs/tasks/manage-hugepages/scheduling-hugepages.md +++ b/content/en/docs/tasks/manage-hugepages/scheduling-hugepages.md @@ -33,7 +33,9 @@ Huge pages can be consumed via container level resource requirements using the resource name `hugepages-`, where size is the most compact binary notation using integer values supported on a particular node. For example, if a node supports 2048KiB page sizes, it will expose a schedulable resource -`hugepages-2Mi`. Unlike CPU or memory, huge pages do not support overcommit. +`hugepages-2Mi`. Unlike CPU or memory, huge pages do not support overcommit. Note +that when requesting hugepage resources, either memory or CPU resources must +be requested as well. ```yaml apiVersion: v1 @@ -53,6 +55,9 @@ spec: resources: limits: hugepages-2Mi: 100Mi + memory: 100Mi + requests: + memory: 100Mi volumes: - name: hugepage emptyDir: