<p>I have one strange issue.</p>
<p>The error that I'm getting is:</p>
<pre><code>unschedulable 0/1 nodes are available insufficient ephemeral-storage
</code></pre>
<p>My requests per workflow that I run in kubernetes are:</p>
<pre><code>resources:
      requests:
        ephemeral-storage: 50Gi
        memory: 8Gi
</code></pre>
<p>And my node capacity is 100GiB per node.</p>
<p>When I run <code>kubectl describe node &lt;node-name&gt;</code> I get the following result:</p>
<pre><code>Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource                    Requests    Limits
  --------                    --------    ------
  cpu                         125m (3%)   0 (0%)
  memory                      8Gi (55%)   0 (0%)
  ephemeral-storage           50Gi (56%)  0 (0%)
  hugepages-1Gi               0 (0%)      0 (0%)
  hugepages-2Mi               0 (0%)      0 (0%)
  attachable-volumes-aws-ebs  0           0
</code></pre>
<p>Do ephemeral-storage and memory overlap? What can be the issue? I cannot resolve.</p>

Miloš Milutinov
<p>In the <code>kubectl describe node</code> output, Kubernetes believes it's used 50 GiB of disk (&quot;ephemeral storage&quot;) and that's 56% of the available resources.  That implies there's about 89 GiB of usable disk space, and about 39 GiB left, so less space than your container claims it needs.</p>
<p>If the node has a 100 GiB disk, space required by the operating system, Kubernetes, and any pulled images counts against that disk capacity before being considered available for ephemeral storage.  You probably will never be able to run two Pods that both require 50 GiB of disk; with the OS overhead they will not both fit at the same time.</p>
<p>(It's also not impossible that the node has 100 GB and not 100 GiB storage.  100 * 10^9 is only 93 * 2^30, which would make that overhead about 4 GiB, which feels a little more typical to me.)</p>
<p>The easiest and &quot;most Kubernetes&quot; option here is to get another node, maybe via the cluster autoscaler.  If you do control the node configuration, changing nodes to more like 120 GB storage would make these Pods fit better.  Especially in an AWS/EKS context, current Kubernetes also supports <a href="https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#generic-ephemeral-volumes" rel="nofollow noreferrer">generic ephemeral volumes</a> which would let you get per-pod storage backed by a volume (on AWS, most likely an EBS volume) rather than fixed-size local disk.</p>
