<p>I have created a Digital Ocean managed Kubernetes cluster following this tutorial very closely. <a href="https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nginx-ingress-with-cert-manager-on-digitalocean-kubernetes" rel="nofollow noreferrer">https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nginx-ingress-with-cert-manager-on-digitalocean-kubernetes</a></p>

<p>Everything is near identical except my custom basic node server container. Furthermore, the cluster works flawlessly until posting a large (>~400Kbs) file/payload to ANY endpoint. </p>

<p>Obviously, I attempted to create this issue running my container outside of Kubernetes and I could not reproduce it at any file size. I also verified that all of my droplets weren't running out of resources. CPU and memory usage were low. </p>

<p>I have seen a few similar issues online with my struggle to find a solution. (ie <a href="https://kubernetes.io/blog/2019/03/29/kube-proxy-subtleties-debugging-an-intermittent-connection-reset/" rel="nofollow noreferrer">https://kubernetes.io/blog/2019/03/29/kube-proxy-subtleties-debugging-an-intermittent-connection-reset/</a>)</p>

<p>I have attempted to apply this DaemonSet and it did not fix the problem.</p>

<p>Has anybody else ran into this issue or found a solution? I tremendously appreciate any help.</p>

<p>Thank you!</p>

<p><strong>UPDATE:</strong> I have tested server with kubectl port-forward and the upload worked correctly. I imagine that would mean it is any issue with my ingress or load balancer. I am still searching for answers.</p>

<p>So, I finally got it! The solution is configuring the proxy body size <code>nginx.ingress.kubernetes.io/proxy-body-size: "50m"</code> as stated here: <a href="https://stackoverflow.com/questions/49918313/413-error-with-kubernetes-and-nginx-ingress-controller">413 error with Kubernetes and Nginx ingress controller</a></p>

<p>Hopefully this can help someone with intermittent connection reset issues on uploads in the future :)</p>
