-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Ingress only exposes internal node ip #50
Comments
The kubernetes node object should have an ExternalIPs field, which i expect we'd be using to populate the status (haven't checked). If we are, then it's wrongfully populated, if we aren't, we should. https://github.com/kubernetes/kubernetes/blob/master/pkg/api/types.go#L2236 |
I meant to link to https://github.com/kubernetes/kubernetes/blob/master/pkg/api/types.go#L2618 |
I'm on GCP, but using the nginx controller. |
https://github.com/kubernetes/ingress/blob/697cf2d8c352b461447cf1a7f265702d3e6be530/core/pkg/k8s/main.go#L57 uses |
what does kubectl get no -o yaml | grep -i external -B 10 (or something to that effect) show? |
@bprashanth
when getting node output. The InternalIP is what shows up in the ingress. |
I realized the diff I showed in the bug report is reversed. This is the actual change I made to fix my issue:
|
@groob I was fixing an issue with the status address for AWS and I saw this. |
Co-authored-by: Song Song Li <[email protected]>
I tried installing this version of the ingress controller today and noticed that the Address listed was
Which is the internal node IP.
I made the following change, which resolves the issue for me, but I'm not sure it's the correct fix
edit: this diff should be reversed I believe. I accidentally switch the
branch..master
order.The text was updated successfully, but these errors were encountered: