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

NGINX ingress controller does not work properly with a named targetPort #743

Closed
paralin opened this issue Apr 8, 2016 · 3 comments · Fixed by #766
Closed

NGINX ingress controller does not work properly with a named targetPort #743

paralin opened this issue Apr 8, 2016 · 3 comments · Fixed by #766

Comments

@paralin
Copy link

paralin commented Apr 8, 2016

When using a named targetPort on the service it does not resolve which endpoint port to use, as far as I can tell.

This is a bit of a hard problem to solve because it's not immediately apparent from the endpoints list what the port name is.

@bprashanth
Copy link

This is a bit of a hard problem to solve because it's not immediately apparent from the endpoints list what the port name is.

https://github.com/kubernetes/kubernetes/blob/master/pkg/api/types.go#L1635
https://github.com/kubernetes/contrib/blob/master/ingress/controllers/nginx/controller.go#L644

@aledbf

@aledbf
Copy link
Contributor

aledbf commented Apr 8, 2016

@paralin can yo provide an example of the yaml you are using?

@aledbf
Copy link
Contributor

aledbf commented Apr 14, 2016

@paralin #781

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.

3 participants