Skip to content

Commit 53f7612

Browse files
authored
Merge pull request #30186 from sandersaares/request-is-not-a-guarantee
A CPU request does not result in a guarantee
2 parents 8f52166 + 667d338 commit 53f7612

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

content/en/docs/concepts/configuration/manage-resources-containers.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -99,9 +99,10 @@ resource requests/limits of that type for each Container in the Pod.
9999
Limits and requests for CPU resources are measured in *cpu* units.
100100
One cpu, in Kubernetes, is equivalent to **1 vCPU/Core** for cloud providers and **1 hyperthread** on bare-metal Intel processors.
101101

102-
Fractional requests are allowed. A Container with
103-
`spec.containers[].resources.requests.cpu` of `0.5` is guaranteed half as much
104-
CPU as one that asks for 1 CPU. The expression `0.1` is equivalent to the
102+
Fractional requests are allowed. When you define a container with
103+
`spec.containers[].resources.requests.cpu` set to `0.5`, you are requesting half
104+
as much CPU time compared to if you asked for `1.0` CPU.
105+
For CPU resource units, the expression `0.1` is equivalent to the
105106
expression `100m`, which can be read as "one hundred millicpu". Some people say
106107
"one hundred millicores", and this is understood to mean the same thing. A
107108
request with a decimal point, like `0.1`, is converted to `100m` by the API, and
@@ -236,7 +237,7 @@ The kubelet also uses this kind of storage to hold
236237
container images, and the writable layers of running containers.
237238

238239
{{< caution >}}
239-
If a node fails, the data in its ephemeral storage can be lost.
240+
If a node fails, the data in its ephemeral storage can be lost.
240241
Your applications cannot expect any performance SLAs (disk IOPS for example)
241242
from local ephemeral storage.
242243
{{< /caution >}}
@@ -440,7 +441,7 @@ Kubernetes does not use them.
440441
Quotas are faster and more accurate than directory scanning. When a
441442
directory is assigned to a project, all files created under a
442443
directory are created in that project, and the kernel merely has to
443-
keep track of how many blocks are in use by files in that project.
444+
keep track of how many blocks are in use by files in that project.
444445
If a file is created and deleted, but has an open file descriptor,
445446
it continues to consume space. Quota tracking records that space accurately
446447
whereas directory scans overlook the storage used by deleted files.

0 commit comments

Comments
 (0)