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

Add Info about OOM Kill (#13723) 

* Add info about OOM Kill

Add details about OOM Kill in case if memory limit is not specified

* Fix Minor Typo
pull/13553/head^2
Abhishek Jaisingh 2019-04-10 06:50:12 +05:30 committed by Kubernetes Prow Robot
parent cb86f99b5b
commit 0173c3a567
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/tasks/configure-pod-container/assign-memory-resource.md
View File

@ -305,7 +305,7 @@ kubectl delete pod memory-demo-3 --namespace=mem-example
If you do not specify a memory limit for a Container, one of the following situations applies:
* The Container has no upper bound on the amount of memory it uses. The Container
could use all of the memory available on the Node where it is running.
could use all of the memory available on the Node where it is running which in turn could invoke the OOM Killer. Further, in case of an OOM Kill, a container with no resource limits will have a greater chance of being killed.
* The Container is running in a namespace that has a default memory limit, and the
Container is automatically assigned the default limit. Cluster administrators can use a