<p>I see these errors in the kubelet.log on my worker nodes</p>
<pre><code>Feb 11 19:39:41 my-node-ip kubelet[4358]: I0711 19:39:41.666680    4358 log.go:198] http: TLS handshake error from 172.16.4.71:58965: EOF
Feb 11 19:39:42 my-node-ip kubelet[4358]: I0711 19:39:42.121386    4358 log.go:198] http: TLS handshake error from 172.16.4.40:21053: EOF
Feb 11 19:39:45 my-node-ip kubelet[4358]: I0711 19:39:45.001122    4358 log.go:198] http: TLS handshake error from 172.16.4.71:36777: EOF
Feb 11 19:39:45 my-node-ip kubelet[4358]: I0711 19:39:45.455301    4358 log.go:198] http: TLS handshake error from 172.16.4.40:31905: EOF
Feb 11 19:39:48 my-node-ip kubelet[4358]: I0711 19:39:48.333620    4358 log.go:198] http: TLS handshake error from 172.16.4.71:1877: EOF
</code></pre>
<ul>
<li>What does the error &quot;http: TLS handshake error from 172.16.4.71:58965: EOF&quot; indicate?</li>
<li>What could be these ips <code>172.16.4.71</code> and <code>172.16.4.40</code> and port correspond to?</li>
</ul>
<p>What should I understand by this error message?</p>

Senthil Kumaran
<p>As mentioned in this <a href="https://aboutssl.org/fix-ssl-tls-handshake-failed-error/" rel="nofollow noreferrer">document</a>:</p>
<blockquote>
<p>Whenever an SSL/TLS Handshake fails, it’s mostly due to certain things going on with the server, website, and the configuration of its installed SSL/TLS. Presently the culprit is TLS configuration as support for SSL 3.0 is deprecated. However, there’s a distinct possibility that a client-side error can be the reason behind the SSL/TLS Handshake Failed error. And, some of the common ones are like incorrect system time or browser updates.</p>
</blockquote>
<p>Also this is an known issue as mentioned in the github <a href="https://github.com/open-policy-agent/gatekeeper/issues/2142" rel="nofollow noreferrer">link</a></p>
<blockquote>
<p>EOF errors seem to be related to a <a href="https://github.com/golang/go/issues/50984" rel="nofollow noreferrer">Go bug</a> and appear on kubernetes 1.22, 1.23 and 1.24. This is not affecting any functional issues and these are generated from core kubernetes. We need to wait until a fix is suggested by kubernetes.</p>
</blockquote>
<p>Can you also try this work around to disable the TLS Handshake errors by following this <a href="https://kubernetes.github.io/ingress-nginx/user-guide/tls/#server-side-https-enforcement-through-redirect" rel="nofollow noreferrer">document</a>.</p>
