<p>When a Pod is evicted I'm supposed to find messages about the eviction at <code>/dev/termination-log</code> (or other path defined in <code>terminationMessagePath</code> property) inside the container filesystem.</p>
<p>I'm trying to track OOMKilled events, but after OOMKilled occured and the Pod was restarted, the <code>/dev/termination-log</code> is empty.<br />
I tried to set <code>terminationMessagePolicy</code> property to <code>FallbackToLogsOnError</code> hoping to find out messages in container log and I did not find anything about the OOMKilled there.</p>
<p>By executing <code>kubectl describe pod podname</code> I can find out that the termination reason was OOMKilled, but I would like to be able to follow this events in order to integrate it with fluentd and logstash.</p>
<p>Our Kubernetes cluster version is v1.9.0 and it's running on-premise. The installation was done using kubeadm on top of CentOS 7.</p>

Matheus Neder
<p>You can ssh to the machine the pod was running and exec <code>journalctl -u kubelet</code></p>
