<p>So I see a related question that wants to control the emptyDir size here:
<a href="https://stackoverflow.com/questions/34610763/setting-kubernetes-emptydir-volume-size">Setting Kubernetes emptyDir volume size</a>.
I see that if this limit gets hit, the pod itself will be evicted.</p>
<p>Also I know know that emptyDir would be half the request RAM. So does that mean if I try to provision 2 or more emptyDir volumes in a pod, it would fail? Or will it just be all virtual memory allocation and I can over-provision in that sense?</p>
<p>What I am possibly trying to get at is that I would want not a hard limit for my volume that would trash the pod itself, but accommodate in RAM if the other volumes are not in use. Of course if the total goes beyond the RAM, I would expect the pod to be trashed.</p>

Aseem Dua
<p><a href="https://kubernetes.io/docs/concepts/storage/volumes/#emptydir" rel="noreferrer"><code>emptyDir</code> volumes</a> are disk-backed by default; there's no particular prohibition against mounting multiple ones.</p>
<p>That documentation also notes:</p>
<blockquote>
<p>However, you can set the <code>emptyDir.medium</code> field to <code>&quot;Memory&quot;</code> [... and if you do ...] any files you write will count against your Container's memory limit.</p>
</blockquote>
<p>So the ordinary pod resource limits apply here: if you set a memory limit, and the combined application memory and tmpfs usage goes above that limit, the pod will get killed.</p>
