Skip to content

Commit f66ac64

Browse files
authored
fix: update note on manage-resources-containers on using milliCPU form (#44003)
Update manage-resources-containers.md Co-authored-by: Qiming Teng <[email protected]> Empty-Commit
1 parent 057c963 commit f66ac64

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

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

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -116,8 +116,13 @@ runs on a single-core, dual-core, or 48-core machine.
116116

117117
{{< note >}}
118118
Kubernetes doesn't allow you to specify CPU resources with a precision finer than
119-
`1m`. Because of this, it's useful to specify CPU units less than `1.0` or `1000m` using
120-
the milliCPU form; for example, `5m` rather than `0.005`.
119+
`1m` or `0.001` CPU. To avoid accidentally using an invalid CPU quantity, it's useful to specify CPU units using the milliCPU form
120+
instead of the decimal form when using less than 1 CPU unit.
121+
122+
For example, you have a Pod that uses `5m` or `0.005` CPU and would like to decrease
123+
its CPU resources. By using the decimal form, it's harder to spot that `0.0005` CPU
124+
is an invalid value, while by using the milliCPU form, it's easier to spot that
125+
`0.5m` is an invalid value.
121126
{{< /note >}}
122127

123128
### Memory resource units {#meaning-of-memory}

0 commit comments

Comments
 (0)