<p>I am trying to bring up an app that was successfully run using docker swarm.  I am using Kubernetes.  I have a master VirtualBox VM and a node both Ubuntu.  The deployment and service with cpu and memory and limits set correctly ( or so I think).  The deployment and service succeeds but kubectl describe pods consistently shows event messages as</p>
<pre class="lang-sh prettyprint-override"><code>0/2 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate, 1 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn't tolerate.
Warning  FailedScheduling  &lt;unknown&gt;  default-scheduler  0/2 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate, 1 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn't tolerate.
</code></pre>
<p>I have checked a few things and increased the disk capacities on the master VM (and worker node though problem is shown only in master).  Reset the worker node using kubeadm and redeployed.</p>
<p>Also went thru similar questions and suggestions.
Looking for suggestions to resolve this toward Pod moving to ready or out of pending state</p>
<p>Thanks</p>
<p>deployment has cpu 500m and limit &quot;1&quot;, memory 1Gi and limit 2Gi</p>

<p>On the master/main, if you really want the pod scheduled there you can try un-tainting it.</p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl taint nodes --all node-role.kubernetes.io/master-
</code></pre>
<p>For the disk pressure taint, you may have something in your control plane from a previous instance of a node with the same name❓ If you know that you have enough space you can force remove it:</p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl taint nodes --all node.kubernetes.io/disk-pressure-
</code></pre>
<p>Keep in mind that this is a taint automatically added by the <a href="https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-based-evictions" rel="nofollow noreferrer">node controller</a>.</p>
<p>✌️</p>
