<p>How to figure out why the taint is set?</p>
<p>Here is my eviction config from kubelet config:</p>
<p>Kubelet-config:</p>
<pre class="lang-yaml prettyprint-override"><code>kubeletArguments:
  eviction-soft:
  - memory.available&lt;100Mi
  - nodefs.available&lt;100Mi
  - nodefs.inodesFree&lt;1%
  - imagefs.available&lt;100Mi
  - imagefs.inodesFree&lt;1%
  eviction-soft-grace-period:
  - memory.available=1m30s
  - nodefs.available=1m30s
  - nodefs.inodesFree=1m30s
  - imagefs.available=1m30s
  - imagefs.inodesFree=1m30s
  eviction-hard:
  - memory.available&lt;100Mi
  - nodefs.available&lt;100Mi
  - nodefs.inodesFree&lt;1%
  - imagefs.available&lt;100Mi
  - imagefs.inodesFree&lt;1%
</code></pre>
<p><code>dh -f</code> output shows that there is 3.8GiB of 20GiB total space available. (&gt;100Mi as configured), so neither soft nor hard eviction threshold is reached. <code>df -i</code> says only 20% of inodes used.</p>
<p>I've tried to figure out the reason by issuing <code>sudo journalctl -u kubelet -b | grep pressure</code> but found nothing useful. Maybe someone could suggest better keywords?</p>

Vitaliy Ivanov
<p>Resolved.
It turned out I used wrong syntax to configure thresholds. Here is correct way to set those:</p>
<pre><code>evictionSoft:
  memory.available: &quot;100Mi&quot;
  nodefs.available: &quot;100Mi&quot;
  nodefs.inodesFree: &quot;1%&quot;
  imagefs.available: &quot;100Mi&quot;
  imagefs.inodesFree: &quot;1%&quot;
evictionSoftGracePeriod:
  memory.available: 5m
  nodefs.available: 5m
  nodefs.inodesFree: 5m
  imagefs.available: 5m
  imagefs.inodesFree: 5m
evictionHard:
  memory.available: &quot;100Mi&quot;
  nodefs.available: &quot;100Mi&quot;
  nodefs.inodesFree: &quot;1%&quot;
  imagefs.available: &quot;100Mi&quot;
  imagefs.inodesFree: &quot;1%&quot;
</code></pre>
<p>(config file is located at <code>/var/lib/kubelet/config.yaml</code> in my case)</p>
<p>Then kubelet needs to be restarted:
<code>sudo systemctl restart kubelet</code></p>
<p>And here is a useful command to get kubelet logs to check if it started correctly: <code>journalctl -u kubelet --since &quot;1min ago&quot;</code></p>
