<p>I got errors in my kube-proxy: </p>

<pre><code>E0107 21:48:57.738867       1 proxysocket.go:160] I/O error: read tcp 10.2.11.253:37568: connection reset by peer
</code></pre>

<p>How can I trace quickly which pod has IP <code>10.2.11.253</code>? And how can I know which request that was, from which pod to which pod?</p>

<p>Or can we change the kube-proxy log level to verbose or debug?</p>

<p>I got another errors, same <code>connection reset</code> error, but the IP is a node's IP</p>

<pre><code>E0107 21:52:53.483363       1 proxysocket.go:160] I/O error: read tcp 192.168.166.180:11732: connection reset by peer
</code></pre>

<p><code>192.168.166.x</code> is my kubernetes node subnet, but how can kube-proxy forwards request to a node IP?</p>

<p>I'm using kubelet 1.0.1 and CoreOS v773.1.0 (docker 1.7.1, kernel 4.1.5) as my cluster nodes.</p>

<p>Thanks for any help!</p>

<p>In my circumstance, it was because kube-proxy (v1.1.4) was missing the <code>--proxy-mode=iptables</code> flag. Evidently in 1.1.4, the default is something other than iptables, and specifying that flag made the logs immediately stop spewing those messages.</p>
