<p>I have a Jenkins deployment pipeline which involves kubernetes plugin. Using kubernetes plugin I create a slave pod for building a node application using <strong>yarn</strong>. The requests and limits for CPU and Memory are set.</p>

<p>When the Jenkins master schedules the slave, sometimes (as I haven’t seen a pattern, as of now), the pod makes the entire node unreachable and changes the status of node to be Unknown. On careful inspection in Grafana, the CPU and Memory Resources seem to be well within the range with no visible spike. The only spike that occurs is with the Disk I/O, which peaks to ~ 4 MiB.</p>

<p>I am not sure if that is the reason for the node unable to address itself as a cluster member. I would be needing help in a few things here:</p>

<p>a) How to diagnose in depth the reasons for node leaving the cluster.</p>

<p>b) If, the reason is Disk IOPS, is there any default requests, limits for IOPS at Kubernetes level?</p>

<p>PS: I am using EBS (gp2)</p>

Arpit Goyal
<p>Considering that the node was previously working and recently stopped showing the ready status restart your kubelet service. Just ssh into the affected node and execute:</p>

<pre><code>/etc/init.d/kubelet restart
</code></pre>

<p>Back on your master node run kubectl get nodes to check if the node is working now</p>
