Update memory limits explanation in Container's resource limits documentation #53630
+5
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Clarified memory limits enforcement details and OOM behaviour.
Description
When describing the OOM Kill behaviour of the Kernel in terminating a container, the phrasing
However, terminations only happen when the kernel detects memory pressure.is ambiguous as memory pressure usually implies Node Pressure rather than the pressure at a cgroup level.This change clarifies that description.
Issue
Closes: #