<p>After creating a simple hello world deployment, my pod status shows as "PENDING". When I run <code>kubectl describe pod</code> on the pod, I get the following:</p>

<pre><code>Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  14s (x6 over 29s)  default-scheduler  0/1 nodes are available: 1 NodeUnderDiskPressure.
</code></pre>

<p>If I check on my node health, I get:</p>

<pre><code>Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  OutOfDisk        False   Fri, 27 Jul 2018 15:17:27 -0700   Fri, 27 Jul 2018 14:13:33 -0700   KubeletHasSufficientDisk     kubelet has sufficient disk space available
  MemoryPressure   False   Fri, 27 Jul 2018 15:17:27 -0700   Fri, 27 Jul 2018 14:13:33 -0700   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     True    Fri, 27 Jul 2018 15:17:27 -0700   Fri, 27 Jul 2018 14:13:43 -0700   KubeletHasDiskPressure       kubelet has disk pressure
  Ready            True    Fri, 27 Jul 2018 15:17:27 -0700   Fri, 27 Jul 2018 14:13:43 -0700   KubeletReady                 kubelet is posting ready status. AppArmor enabled
</code></pre>

<p>So it seems the issue is that "kubelet has disk pressure" but I can't really figure out what that means. I can't SSH into minikube and check on its disk space because I'm using VMWare Workstation with <code>--vm-driver=none</code>.</p>

<p>This is an old question but I just saw it and because it doesn't have an answer yet, I will write my answer.</p>
<p>I was facing this problem and my pods were getting evicted many times because of disk pressure and different commands such as <code>df</code> or <code>du</code> were not helpful.</p>
<p>With the help of the answer that I wrote <a href="https://serverfault.com/a/994413/509898">here</a>, I found out that the main problem is the log files of the pods and because K8s is not supporting log rotation they can grow to hundreds of Gigs.</p>
<p>There are different log rotation methods available but I currently I am searching for the best practice for K8s so I can't suggest any specific one, yet.</p>
<p>I hope this can be helpful.</p>
