Setting limits is useful to stop over-committing resources and protect other deployments from resource starvation. Notice how your application has 256MB of memory guaranteed, but it can grow up until 1GB of memory.Īfter that, it is stopped or throttled by Kubernetes. Your application might require at least 256MB of memory, but you might want to be sure that it doesn't consume more than 1GB of memory. On the other hand, limits define the max amount of resources that the container can consume. The application can use more than 256MB, but Kubernetes guarantees a minimum of 256MB to the container.
If you think that your app requires at least 256MB of memory to operate, this is the request value. Requests define the minimum amount of resources that containers need.
There are two different types of resource configurations that can be set on each container of a pod. In this blog, you will explore setting resource limits for a Flask web service automatically using the Vertical Pod Autoscaler and the metrics server. TL DR: In Kubernetes resource constraints are used to schedule the Pod in the right node, and it also affects which Pod is killed or starved at times of high load.
