<p>I get this error when i tried to deploy one deployment with ten replicas.</p>

<blockquote>
  <p>0/2 nodes are available: 1 Insufficient memory, 1 node(s) had taints that the pod didn't tolerate.</p>
</blockquote>

<p>I don't understand why two node. Is the same node and just the same problem.</p>

<p>I have a lot of RAM (1GB) free. </p>

<p>How can i fix this error with out add another node.</p>

<p>I have in deployment yaml file this for resources:</p>

<p>limits:
    cpu: 1000m
    memory: 1000Mi
  requests:
    cpu: 100m
    memory: 200Mi</p>

<p>Server:</p>

<ol>
<li><p>Master: </p>

<pre><code>CPU: 2
RAM: 2 - 1 Free
</code></pre></li>
<li><p>Slave:</p>

<pre><code>CPU: 2
RAM: 2 - 1 Free
</code></pre></li>
</ol>

<p>I think you have multiple issues here.</p>

<p>First to the format of the error message you get </p>

<blockquote>
  <p>0/2 nodes are available: 1 Insufficient memory, 1 node(s) had taints that the pod didn't tolerate.</p>
</blockquote>

<p>The first thing is clear you have 2 nodes in total an could not schedule to any of them. Then comes a list of conditions which prevent the scheduling on that node. One node can be affected by multiple issues. For example, low memory and insufficient CPU. So, the numbers can add up to more than what you have on total nodes.</p>

<p>The second issue is that the requests you write into your YAML file apply per replica. If you instantiate the same pod with 100M Memory 5 times they need 500M in total. You want to run 10 pods which request each 200Mi memory. So, you need 2000Mi free memory.</p>

<p>Your error message already implies that there is not enough memory on one node. I would recommend you inspect both nodes via <code>kubectl describe node &lt;node-name&gt;</code> to find out how much free memory Kubernetes "sees" there. Kubernetes always blocks the full amount of memory a pod requests regardless how much this pod uses.</p>

<p>The taints in your error message tells that the other node, possibly the master, has a taint which is not tolerated by the deployment. For more about taints and tolerations see the <a href="https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/" rel="noreferrer">documentation</a>. In short find out which taint on the node prevents the scheduling and remove it via <code>kubectl taint nodes &lt;node-name&gt; &lt;taint-name&gt;-</code>.</p>
