<p>I run node-exporter as a daemonset inside AWS EKS and found today that it's present on 10 nodes, however my cluster has 13 nodes.</p>
<p>How do I make sure it also runs on 3 missed nodes?</p>

DmitrySemenov
<p>Tolerate the daemonset using:</p>
<pre><code>tolerations:        
  - effect: NoSchedule         
    operator: Exists
</code></pre>
<p>Per <a href="https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/" rel="nofollow noreferrer">Docs</a> DeamonSets already have a few tolerations by default. The no-key one I posted is making sure you are covering all possible reasons of <code>NoSchedule</code>:</p>
<blockquote>
<p>An empty key with operator Exists matches all keys, values and effects
which means this will tolerate everything.</p>
</blockquote>
<p>This is a commonly used setting for monitoring daemons and log collectors.</p>
