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

Merge pull request #48596 from fgogolli/patch-2 

Fix typos and text in manage-resources-containers.md
pull/48673/head
Kubernetes Prow Robot 2024-11-10 00:46:43 +00:00 committed by GitHub
parent 3fa049b277 dbc57ad602
commit f7f347ca0e
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

6
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)
@ -255,8 +255,8 @@ more likely.
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