<p>i am getting </p>

<pre><code>0/7 nodes are available: 2 node(s) had taints that the pod didn't tolerate, 5 node(s) had volume node affinity conflict. 
</code></pre>

<p>for my prometheus server pod but if i check each nodes there are no taints. and there is enough cpu and memory to be allocated.. what am i missing here?</p>

<p>i tried deleting the pods and even the deployment object but the error still persists</p>

<p>all nodes have 0 taints..
this is a fresh prometheus install on a new kubernetes cluster
the yaml files that i have used to work until now when i needed to deploy a new kubernetes cluster</p>

markrosario
<blockquote>
  <p>0/7 nodes are available: 2 node(s) had taints that the pod didn't tolerate, 5 node(s) had volume node affinity conflict. </p>
</blockquote>

<p>The message is specific: it's not the <em>taints</em> that are keeping your prometheus pods off of your workers, it's the <strong>volume</strong> that is the problem. If you are in AWS, it's because your volume is in an availability zone that your workers are not (so, a <code>us-west-2a</code> volume and <code>us-west-2c</code> workers, for example)</p>

<p>The shortest path to success in your situation may be to either recreate the volume in the correct A.Z. if it was empty, or manually create a new volume and copy the data into an A.Z. that matches your workers, or (of course) spin up a new worker in the A.Z. that matches the volume</p>

<blockquote>
  <p>all nodes have 0 taints..</p>
</blockquote>

<p>Is for sure not true for two reasons: because the scheduler clearly says there are two Nodes with taints, and because unless you specifically stripped them off, the masters are almost always(?) provisioned with <code>node.kubernetes.io/master:NoSchedule</code> taints explicitly to keep workloads off of them</p>
