From 47a07818640f4ce10b00e861b7ef5de8dde4c088 Mon Sep 17 00:00:00 2001 From: Qiming Teng Date: Thu, 16 Nov 2017 16:43:06 +0800 Subject: [PATCH] Note on creating LimitRange for GPU, huge-pages resources --- docs/tasks/administer-cluster/cpu-constraint-namespace.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/tasks/administer-cluster/cpu-constraint-namespace.md b/docs/tasks/administer-cluster/cpu-constraint-namespace.md index 40c4961832..f5f4d7dadd 100644 --- a/docs/tasks/administer-cluster/cpu-constraint-namespace.md +++ b/docs/tasks/administer-cluster/cpu-constraint-namespace.md @@ -79,6 +79,11 @@ CPU request and limit to the Container. * Verify that the Container specifies a CPU limit that is less than or equal to 800 millicpu. +**Note:** When creating a `LimitRange` object, you can specify limits on huge-pages +or GPUs as well. However, when both `default` and `defaultRequest` are specified +on these resources, the two values must be the same. +{: .note} + Here's the configuration file for a Pod that has one Container. The Container manifest specifies a CPU request of 500 millicpu and a CPU limit of 800 millicpu. These satisfy the minimum and maximum CPU constraints imposed by the LimitRange.