<p>Is there a recommended minimum size (or minimum number of inodes) for the <code>/tmp</code> file system (partition) on Kubernetes cluster nodes?</p>

<p>What I am experiencing (on a bare-metal Kubernetes 1.16.3 cluster) is that cluster nodes hit 100% inodes used (according to <code>df -i</code>). This has some negative effects (as one would expect; e.g. <code>kubectl exec ... bash</code> into pods on concerned nodes leads to "no space left on device") but <code>kubectl get nodes</code> (strangely) still reports these nodes as "Ready". The <code>/tmp</code> file systems involved are relatively small, i.e. 2G (121920 inodes) and 524M (35120 inodes) respectively.</p>

<p>There is no recommended minimum size for kubernetes. The defaults are good for most cases but is you are creating e.g. many of empty files you might eventually run out of inodes. If you need more you need to manually adjust its number.</p>
