You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.
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
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:
From what I can tell, this causes issues when combined with the
proxy_next_upstream
flag in nginx for bigger server configs like:Is it possible to de-dup this server list or is this for some reason intentional?
The text was updated successfully, but these errors were encountered: