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

Fixing yaml (#10541)

Browse Source 
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".
This commit is contained in:
Cliff Burdick
2018-11-18 18:38:22 -08:00
committed by k8s-ci-robot
parent 8790759a24
commit b5a09f68de
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/manage-hugepages/scheduling-hugepages.md
+6 -1
View File
@@ -33,7 +33,9 @@ Huge pages can be consumed via container level resource requirements using the
resource name `hugepages-<size>`, where size is the most compact binary notation resource name `hugepages-<size>`, where size is the most compact binary notation
using integer values supported on a particular node. For example, if a node using integer values supported on a particular node. For example, if a node
supports 2048KiB page sizes, it will expose a schedulable resource 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 ```yaml
apiVersion: v1 apiVersion: v1
@@ -53,6 +55,9 @@ spec:
resources: resources:
limits: limits:
hugepages-2Mi: 100Mi hugepages-2Mi: 100Mi
memory: 100Mi
requests:
memory: 100Mi
volumes: volumes:
- name: hugepage - name: hugepage
emptyDir: emptyDir: