Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[nginx] Nginx template duplicates upstreams. #455

Closed
Farit-Biktimirov opened this issue Mar 16, 2017 · 5 comments · Fixed by #456
Closed

[nginx] Nginx template duplicates upstreams. #455

Farit-Biktimirov opened this issue Mar 16, 2017 · 5 comments · Fixed by #456

Comments

@Farit-Biktimirov
Copy link

Farit-Biktimirov commented Mar 16, 2017

Is it a normal behaviour for nginx templator to duplicate upstreams:

upstream qa-service-health-port {
least_conn;
server 10.12.16.8:18080 max_fails=0 fail_timeout=0;
server 10.12.16.8:18080 max_fails=0 fail_timeout=0;
server 10.12.16.8:18080 max_fails=0 fail_timeout=0;
server 10.12.16.8:18080 max_fails=0 fail_timeout=0;
server 10.13.192.4:18080 max_fails=0 fail_timeout=0;
server 10.13.192.4:18080 max_fails=0 fail_timeout=0;
server 10.13.192.4:18080 max_fails=0 fail_timeout=0;
server 10.13.192.4:18080 max_fails=0 fail_timeout=0;
}

Is there any workaround to mitigate that?

@aledbf
Copy link
Member

aledbf commented Mar 16, 2017

@Farit-Biktimirov please check if the image quay.io/aledbf/nginx-ingress-controller:0.78 solves this issue.

@Farit-Biktimirov
Copy link
Author

@aledbf that is awesome. I'll try image noted above.

@MaikuMori
Copy link

MaikuMori commented Mar 16, 2017

Could this be connected with #448 ?

EDIT: You beat me to it.

@aledbf
Copy link
Member

aledbf commented Mar 16, 2017

@MaikuMori yes. With #456, this and #448 are fixed

@aledbf
Copy link
Member

aledbf commented Mar 16, 2017

@MaikuMori please test quay.io/aledbf/nginx-ingress-controller:0.78 to confirm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants