<p>I am trying to deploy a pod and copy 10GB of TPCDS data into the pod.
I am using a PVC with storage capacity of 50 GB.
My specifications are:</p>
<pre class="lang-yaml prettyprint-override"><code>resources:
        limits:
          cpu: &quot;1&quot;
          memory: 20Gi
          #ephemeral-storage: 20Gi
        requests:
          cpu: &quot;1&quot;
          memory: 20Gi
</code></pre>
<p>But still I am facing this issue while copying data into the pod.</p>
<pre class="lang-none prettyprint-override"><code>The node was low on resource: ephemeral-storage. Container spark-kafka-cont was using 10542048Ki, which exceeds its request of 0.
</code></pre>

Abhik NASKAR
<p>Your issue is related to the present running pods that must be terminated due to insufficient disk space. <code>Updating to a bigger disk helps to delay the eviction process.</code></p>
<p>Looks like that particular node does not have enough storage available. Suggest you to explicitly specify the local ephemeral storage request and limit (<code>set limits/requests on ephemeral-storage on all your workloads</code>), so that kubernetes will respect that. Otherwise, it is possible that the pod will get evicted. Refer to official docs on <a href="https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#local-ephemeral-storage" rel="nofollow noreferrer">Local ephemeral storage</a> &amp; <a href="https://kubernetes.io/blog/2022/09/19/local-storage-capacity-isolation-ga/" rel="nofollow noreferrer">Local Storage Capacity Isolation Reaches GA</a> for details.</p>
<p>To understand and resolve your issue quickly, use <code>kubectl top</code> command to list all the running nodes and pods along with their resource utilization. And also <code>kubectl exec</code> to get a shell in the pod, and then use normal Unix commands like</p>
<p><code>du -sh</code> [run inside a container] <code>df -h</code>
and <code>du -h someDir</code> commands to find where more space is being utilized. ​​​​​​​Sometimes disk space is taken by <code>logs or emptyDir</code> that are causing this issue. Just get an external volume, map it into the container, and get the logs outside of the node. Using the <code>kubectl logs</code> command helps to find out these logs. Check processes you may be configured to log to a file, In that case set your logging setup to log to stdout.</p>
