From 0173c3a5677037bc567179b3d0ddee8a8a8fa104 Mon Sep 17 00:00:00 2001 From: Abhishek Jaisingh Date: Wed, 10 Apr 2019 06:50:12 +0530 Subject: [PATCH] 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 --- .../tasks/configure-pod-container/assign-memory-resource.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/configure-pod-container/assign-memory-resource.md b/content/en/docs/tasks/configure-pod-container/assign-memory-resource.md index 0f418370c3..e8f7d8073a 100644 --- a/content/en/docs/tasks/configure-pod-container/assign-memory-resource.md +++ b/content/en/docs/tasks/configure-pod-container/assign-memory-resource.md @@ -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