<p>I created a single master and 2 worker cluster using Kops on AWS. Now for my experiment, I need to kill the pod on a worker and check the kubelet logs to know:</p>
<p>When the pod was removed from service endpoint list?</p>
<p>When a new pod container got recreated?</p>
<p>When the new pod container was assigned the new IP Address?</p>
<p>While when I created an on-prem cluster using kubeadm, I could see all the information (like the one mentioned above) in the kubelet logs of the worker node (whose pod was killed).</p>
<p>I do not see detailed kubelet logs like this, specially logs related to assignment of IP address in Kops created K8s cluster.</p>
<p>How to get the information mentioned above in the cluster created using kops?</p>

Shresthi Garg
<p>On the machines with systemd both the kubelet and container runtime write to <code>journald</code>. If systemd is not present they write to <code>.log</code> in the <code>/var/log</code> location.</p>
<p>You can access the systemd logs with <code>journalctl</code> command:</p>
<pre class="lang-sh prettyprint-override"><code>journalctl -u kubelet
</code></pre>
<p>This information of course has to be collected after login into desired node.</p>
