Upstream Pod Scaling Closes Connections

[trumpet2012]

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.): Yes

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):

reloading, dropped connections

I found this closed issue: #489. They seemed to be having a similar problem.

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report

NGINX Ingress controller version: 0.11.0

Kubernetes version (use kubectl version): v1.7.4

Environment:

• Cloud provider or hardware configuration: AWS
• OS (e.g. from /etc/os-release): Debian GNU/Linux 8 (jessie)
• Kernel (e.g. uname -a): Linux 4.4.78-k8s #1 SMP Fri Jul 28 01:28:39 UTC 2017 x86_64 GNU/Linux
• Install tools:
• Others:

What happened:
Pod scaling seems to close connections.

What you expected to happen:
Connections should not be closed when pods are added/removed from the ingress.

How to reproduce it (as minimally and precisely as possible):
Begin uploading a large file. While the file is uploading, scale the upstream pods. This causes the upload to get reset.

Anything else we need to know:
Enabling the service-upstream annotation resolved the issue. However then we would lose the load balancing capabilities of nginx.

[aledbf]

Closing. This works as expected. That said after #2174 this should not be an issue. You can test that If using quay.io/aledbf/nginx-ingress-controller:0.341 with the flag --enable-dynamic-configuration=true in the deployment