Skip to content

Commit 314ad4c

Browse files
authored
Merge pull request #32326 from nirroz93/patch-2
Changing note about limits without requests
2 parents f57b6a4 + 76e7844 commit 314ad4c

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

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

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -47,10 +47,9 @@ or by enforcement (the system prevents the container from ever exceeding the lim
4747
runtimes can have different ways to implement the same restrictions.
4848

4949
{{< note >}}
50-
If a container specifies its own memory limit, but does not specify a memory request, Kubernetes
51-
automatically assigns a memory request that matches the limit. Similarly, if a container specifies its own
52-
CPU limit, but does not specify a CPU request, Kubernetes automatically assigns a CPU request that matches
53-
the limit.
50+
If you specify a limit for a resource, but do not specify any request, and no admission-time
51+
mechanism has applied a default request for that resource, then Kubernetes copies the limit
52+
you specified and uses it as the requested value for the resource.
5453
{{< /note >}}
5554

5655
## Resource types

0 commit comments

Comments
 (0)