<p>It is known that if a pod consumed more resource than <code>request</code>, it is likely to be evicted or terminated. What is the purpose of <code>resource limit</code> then? Is it like a grace period? </p>

<pre><code>  resources: 
    requests:
      cpu: "100m"
    limits:
      cpu: "200m"
</code></pre>

<p>I didn't see a clear documentation for this in Kubernetes official doc. Can anyone clarify this?</p>

<p>Request guarantees a <a href="https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#how-pods-with-resource-requests-are-scheduled" rel="nofollow noreferrer">minimum amount of resource</a>, which the scheduler does by ensuring the node that the Pod is scheduled to has space for it. Limit is a <a href="https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#how-pods-with-resource-limits-are-run" rel="nofollow noreferrer">maximum over which a Pod is like to be killed</a>.</p>

<p>I personally find the <a href="https://cloud.google.com/blog/products/gcp/kubernetes-best-practices-resource-requests-and-limits" rel="nofollow noreferrer">google kubernetes documentation clearer on this</a> than the official kubernetes one.</p>
