<p>I'm using EKS (Kubernetes) in AWS and I have problems with posting a payload at around 400 Kilobytes to any web server that runs in a container in that Kubernetes. I hit some kind of limit but it's not a limit in size, it seems at around 400 Kilobytes many times works but sometimes I get (testing with Python requests)</p>

<pre><code>requests.exceptions.ChunkedEncodingError: ("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer'))
</code></pre>

<p>I test this with different containers (python web server on Alpine, Tomcat server on CentOS, nginx, etc).</p>

<p>The more I increase the size over 400 Kilobytes, the more consistent I get: Connection reset by peer.</p>

<p>Any ideas?</p>

<p>Thanks for your answers and comments, helped me get closer to the source of the problem. I did upgrade the AWS cluster from 1.11 to 1.12 and that cleared this error when accessing from service to service within Kubernetes. However, the error still persisted when accessing from outside the Kubernetes cluster using a public dns, thus the load balancer. 
So after testing some more I found out that now the problem lies in the ALB or the ALB controller for Kubernetes: <a href="https://kubernetes-sigs.github.io/aws-alb-ingress-controller/" rel="noreferrer">https://kubernetes-sigs.github.io/aws-alb-ingress-controller/</a>
So I switched back to a Kubernetes service that generates an older-generation ELB and the problem was fixed. The ELB is not ideal, but it's a good work-around for the moment, until the ALB controller gets fixed or I have the right button to press to fix it.</p>
