kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix typos and text in manage-resources-containers.md 

Fix typos and text in manage-resources-containers.md
pull/48596/head
Flamur Gogolli 2024-10-30 17:02:04 +01:00 committed by GitHub
parent c37054ee0d
commit dbc57ad602
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -199,7 +199,7 @@ On Linux, the container runtime typically configures
kernel {{< glossary_tooltip text="cgroups" term_id="cgroup" >}} that apply and enforce the kernel {{< glossary_tooltip text="cgroups" term_id="cgroup" >}} that apply and enforce the
limits you defined. limits you defined.
- The CPU limit defines a hard ceiling on how much CPU time that the container can use. - The CPU limit defines a hard ceiling on how much CPU time the container can use.
During each scheduling interval (time slice), the Linux kernel checks to see if this During each scheduling interval (time slice), the Linux kernel checks to see if this
limit is exceeded; if so, the kernel waits before allowing that cgroup to resume execution. limit is exceeded; if so, the kernel waits before allowing that cgroup to resume execution.
- The CPU request typically defines a weighting. If several different containers (cgroups) - The CPU request typically defines a weighting. If several different containers (cgroups)
@ -244,30 +244,30 @@ directly or from your monitoring tools.
If you do not specify a `sizeLimit` for an `emptyDir` volume, that volume may If you do not specify a `sizeLimit` for an `emptyDir` volume, that volume may
consume up to that pod's memory limit (`Pod.spec.containers[].resources.limits.memory`). consume up to that pod's memory limit (`Pod.spec.containers[].resources.limits.memory`).
If you do not set a memory limit, the pod has no upper bound on memory consumption, If you do not set a memory limit, the pod has no upper bound on memory consumption,
and can consume all available memory on the node. Kubernetes schedules pods based and can consume all available memory on the node. Kubernetes schedules pods based
on resource requests (`Pod.spec.containers[].resources.requests`) and will not on resource requests (`Pod.spec.containers[].resources.requests`) and will not
consider memory usage above the request when deciding if another pod can fit on consider memory usage above the request when deciding if another pod can fit on
a given node. This can result in a denial of service and cause the OS to do a given node. This can result in a denial of service and cause the OS to do
out-of-memory (OOM) handling. It is possible to create any number of `emptyDir`s out-of-memory (OOM) handling. It is possible to create any number of `emptyDir`s
that could potentially consume all available memory on the node, making OOM that could potentially consume all available memory on the node, making OOM
more likely. more likely.
{{< /caution >}} {{< /caution >}}
From the perspective of memory management, there are some similarities between From the perspective of memory management, there are some similarities between
when a process uses memory as a work area and when using memory-backed when a process uses memory as a work area and when using memory-backed
`emptyDir`. But when using memory as a volume like memory-backed `emptyDir`, `emptyDir`. But when using memory as a volume, like memory-backed `emptyDir`,
there are additional points below that you should be careful of. there are additional points below that you should be careful of:
* Files stored on a memory-backed volume are almost entirely managed by the * Files stored on a memory-backed volume are almost entirely managed by the
user application. Unlike when used as a work area for a process, you can not user application. Unlike when used as a work area for a process, you can not
rely on things like language-level garbage collection. rely on things like language-level garbage collection.
* The purpose of writing files to a volume is to save data or pass it between * The purpose of writing files to a volume is to save data or pass it between
applications. Neither Kubernetes nor the OS may automatically delete files applications. Neither Kubernetes nor the OS may automatically delete files
from a volume, so memory used by those files can not be reclaimed when the from a volume, so memory used by those files can not be reclaimed when the
system or the pod are under memory pressure. system or the pod are under memory pressure.
* A memory-backed `emptyDir` is useful because of its performance, but memory * A memory-backed `emptyDir` is useful because of its performance, but memory
is generally much smaller in size and much higher in cost than other storage is generally much smaller in size and much higher in cost than other storage
media, such as disks or SSDs. Using large amounts of memory for `emptyDir` media, such as disks or SSDs. Using large amounts of memory for `emptyDir`
volumes may affect the normal operation of your pod or of the whole node, volumes may affect the normal operation of your pod or of the whole node,
so should be used carefully. so should be used carefully.