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

A CPU request does not result in a guarantee

Browse Source 
It is merely a pod placement constraint but the phrasing leads readers to  the incorrect understanding that some actual CPU time is guaranteed/reserved. Re-phrase to make it clear this is nothing more than a request.
This commit is contained in:
Sander Saares
2021-10-22 09:02:42 +03:00
parent 66d9eb730d
commit 3f5ab3f982
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/configuration/manage-resources-containers.md
+1 -1
View File
@@ -100,7 +100,7 @@ Limits and requests for CPU resources are measured in *cpu* units.
One cpu, in Kubernetes, is equivalent to **1 vCPU/Core** for cloud providers and **1 hyperthread** on bare-metal Intel processors. One cpu, in Kubernetes, is equivalent to **1 vCPU/Core** for cloud providers and **1 hyperthread** on bare-metal Intel processors.
Fractional requests are allowed. A Container with Fractional requests are allowed. A Container with
`spec.containers[].resources.requests.cpu` of `0.5` is guaranteed half as much `spec.containers[].resources.requests.cpu` of `0.5` asks for half as much
CPU as one that asks for 1 CPU. The expression `0.1` is equivalent to the CPU as one that asks for 1 CPU. The expression `0.1` is equivalent to the
expression `100m`, which can be read as "one hundred millicpu". Some people say expression `100m`, which can be read as "one hundred millicpu". Some people say
"one hundred millicores", and this is understood to mean the same thing. A "one hundred millicores", and this is understood to mean the same thing. A