问题原文
原帖链接 · spondbob · CC BY-SA 3.0
I have a situation with ip_hash on nginx for sticky session where it always direct the traffic to one server only. The nginx is running behind a Google Cloud load balancer, from nginx it hits my app's GC Kubernetes load balancer before actually going to one of the pod.
I have a thought that all users' IP was masked by GC load balancer so that nginx recognises them as one source.
I was told that we can add user's original IP to nginx's header so that the load balancer able to recognise them as different users. How can I approach one? Or is there another solution?
已采纳解答
原帖链接 · cryotek · CC BY-SA 3.0
If you are using Network load balancing (with target pools) the load balancer keeps the IP. What happens is that Kubernetes is changing the source IP with the cluster/node IPs.
Kubernetes has a feature to preserve the client source IP. You can check in the docs for how to preserve the client source IP in the services with Type=LoadBalancer (Network load balancing).
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
