Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

Ingress servers duplicated when multiple ingresses #858

Closed
mikesplain opened this issue Apr 27, 2016 · 2 comments · Fixed by #766
Closed

Ingress servers duplicated when multiple ingresses #858

mikesplain opened this issue Apr 27, 2016 · 2 comments · Fixed by #766

Comments

@mikesplain
Copy link

mikesplain commented Apr 27, 2016

When I test against the ingress controller in https://github.com/kubernetes/contrib/tree/master/ingress/controllers/nginx, using the ingresses in https://github.com/kubernetes/contrib/blob/master/ingress/controllers/nginx/examples/ingress.yaml, multiple of each IP are listed the server config of nginx:

    upstream default-echoheaders-x-80 {
        least_conn;
        server 10.138.27.3:8080;
        server 10.138.27.3:8080;

    }

    upstream default-echoheaders-y-80 {
        least_conn;
        server 10.138.27.3:8080;

    }

From what I can tell, this causes issues when combined with the proxy_next_upstream flag in nginx for bigger server configs like:
nginx vhost traffic status monitor 2016-04-27 16-21-41

Is it possible to de-dup this server list or is this for some reason intentional?

@aledbf
Copy link
Contributor

aledbf commented Apr 27, 2016

is this for some reason intentional?

No, is not intentional. Different upstreams will have a different server list. In this case the services default-echoheaders-x-80 and default-echoheaders-y-80 uses the same endpoints.

Let me see if I can reproduce the duplication in the upstream of default-echoheaders-x-80

@mikesplain
Copy link
Author

@aledbf Great thanks, let me know if you need anything from me.

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

Successfully merging a pull request may close this issue.

2 participants