<p>I've introduced a bunch of readiness and liveness checks in our Kubernetes pods. And apart from currently being fairly CPU-heavy. They appear to work as expected.</p>

<p>But then we started to run some load-testing on our solution. And almost immediately pods gets killed and event like this show up:</p>

<p><code>Liveness probe errored: read tcp 10.244.27.123:8080: use of closed network connection</code></p>

<p>There appear to have been an issue with keep-alive and the http probe (<a href="https://github.com/kubernetes/kubernetes/issues/15643" rel="nofollow">issue 15643</a>). But that also appears to have been fixed by disabling keep-alive in the probe in Kubernetes 1.1.1 (which is what we are running)</p>

<p>So does anyone have any idea what could be going on?</p>

<p>I have seen this error when the liveness probe is timing out. Try lengthening the timeoutSeconds on your livenessProbe and see if the problem goes away.</p>
