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.
What keywords did you search in NGINX Ingress controller issues before filing this one?
(If you have found any duplicates, you should instead reply there.):
Kernel (e.g. uname -a): Linux rancher 4.4.0-135-generic #161-Ubuntu SMP Mon Aug 27 10:45:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Install tools: Rancher 2.1.1
Others:
What happened:
The Nginx ingress does not have a private IP from canal. And when it communicates with services, it uses the instance public IP instead of using the internal network for some reason.
kubectl get ingress
NAME HOSTS ADDRESS PORTS AGE
example-ingress example.com 111.22.33.44 80 5m
I need to detect the nginx ingress range to whitelist it as a proxy for my webserver, so I can get the real remote IP.
I tried both the nginx ingress that comes with Rancher and with helm to enable --report-node-internal-ip-address=true:
The exact same setup works fine on a kubeadm setup. But without setting ClusterIP,controller.hostNetwork=true,controller.extraArgs.report-node-internal-ip-address=true
If I do not use hostNetwork=true then the ingress doesn't work.
What you expected to happen:
I should see the private IP of pod instead of the public IP
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
Issue actions