whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix nits in the garbage collection page

Browse Source 
Some nits fixed in this PR:

- The typo of 'MaxContainers' and 'MaxPerPodContainer';
- The section name which should be 'Container garbage collection' rather
  than 'Container image garbage collection'.
This commit is contained in:
Qiming Teng
2022-01-03 21:14:31 +08:00
parent 0a474e749a
commit 757915ae99
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/architecture/garbage-collection.md
+4 -4
View File
@@ -137,7 +137,7 @@ collection, which deletes images in order based on the last time they were used,
starting with the oldest first. The kubelet deletes images starting with the oldest first. The kubelet deletes images
until disk usage reaches the `LowThresholdPercent` value. until disk usage reaches the `LowThresholdPercent` value.
### Container image garbage collection {#container-image-garbage-collection} ### Container garbage collection {#container-image-garbage-collection}
The kubelet garbage collects unused containers based on the following variables, The kubelet garbage collects unused containers based on the following variables,
which you can define: which you can define:
@@ -152,11 +152,11 @@ which you can define:
In addition to these variables, the kubelet garbage collects unidentified and In addition to these variables, the kubelet garbage collects unidentified and
deleted containers, typically starting with the oldest first. deleted containers, typically starting with the oldest first.
`MaxPerPodContainer` and `MaxContainer` may potentially conflict with each other `MaxPerPodContainer` and `MaxContainers` may potentially conflict with each other
in situations where retaining the maximum number of containers per Pod in situations where retaining the maximum number of containers per Pod
(`MaxPerPodContainer`) would go outside the allowable total of global dead (`MaxPerPodContainer`) would go outside the allowable total of global dead
containers (`MaxContainers`). In this situation, the kubelet adjusts containers (`MaxContainers`). In this situation, the kubelet adjusts
`MaxPodPerContainer` to address the conflict. A worst-case scenario would be to `MaxPerPodContainer` to address the conflict. A worst-case scenario would be to
downgrade `MaxPerPodContainer` to `1` and evict the oldest containers. downgrade `MaxPerPodContainer` to `1` and evict the oldest containers.
Additionally, containers owned by pods that have been deleted are removed once Additionally, containers owned by pods that have been deleted are removed once
they are older than `MinAge`. they are older than `MinAge`.
@@ -180,4 +180,4 @@ configure garbage collection:
* Learn more about [ownership of Kubernetes objects](/docs/concepts/overview/working-with-objects/owners-dependents/). * Learn more about [ownership of Kubernetes objects](/docs/concepts/overview/working-with-objects/owners-dependents/).
* Learn more about Kubernetes [finalizers](/docs/concepts/overview/working-with-objects/finalizers/). * Learn more about Kubernetes [finalizers](/docs/concepts/overview/working-with-objects/finalizers/).
* Learn about the [TTL controller](/docs/concepts/workloads/controllers/ttlafterfinished/) (beta) that cleans up finished Jobs. * Learn about the [TTL controller](/docs/concepts/workloads/controllers/ttlafterfinished/) (beta) that cleans up finished Jobs.