5

Our Kubernetes cluster includes an nginx load balancer that forwards the requests to other pods.

However, the nginx sees local source IPs and therefore cannot set the correct X-Real-IP header. I tried setting the externalTrafficPolicy value of nginx to "Local" but the IP does not change.

Section of the nginx service config:

 "selector": {
  "app": "nginx-ingress",
  "component": "controller",
  "release": "loping-lambkin"
},
"clusterIP": "10.106.1.182",
"type": "LoadBalancer",
"sessionAffinity": "None",
"externalTrafficPolicy": "Local",
"healthCheckNodePort": 32718

Result:

GET / HTTP/1.1
Host: example.com:444
X-Request-ID: dd3310a96bf154d2ac38c8877dec312c
X-Real-IP: 10.39.0.0
X-Forwarded-For: 10.39.0.0

We use a bare metal cluster with metallb.

aitorhh
  • 2,331
  • 1
  • 23
  • 35
Johannes Mittendorfer
  • 1,102
  • 10
  • 17

2 Answers2

1

I found out that weave needs to be configured using NO_MASQ_LOCAL=1 to respect the externalTrafficPolicy property

Johannes Mittendorfer
  • 1,102
  • 10
  • 17
0

This appears to be a bug in the IPVS implementation for services of type LoadBalancer : https://github.com/google/metallb/issues/290

eknudtson
  • 1