NLB with NGINX Ingress Controller is overwriting client IP, how to retain actual client IP

Question

I have an EKS setup with some web applications/websites served by pods which have Nginx Ingress Controller with NLB for TLS termination.
Problem is that the logs on some applications show ips of EKS Worker Nodes, instead of retaining the original requester IP.
Would like to retain them for further processing of requests.

Was Trying with this digital Ocean Doc,
https://docs.digitalocean.com/support/how-do-i-enable-proxy-protocol-when-my-load-balancer-sends-requests-to-the-nginx-ingress-controller/
by setting configmap variable as:- use-proxy-protocol: "true"
but it impaired the system, untill rolledback.

Accepted Answer

Hi,

To make it work, you need to have proxy protocol enabled on your NLB and have the appropriate configuration in ingress-nginx.

Here is an example of ingress-nginx, it expects that you have aws-load-balancer controller installed in your cluster.
```
controller:
  config:
    use-proxy-protocol: "true"
    real-ip-header: "proxy_protocol"
    use-forwarded-headers: "true"
  service:
    annotations:
      service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: "*"
      service.beta.kubernetes.io/aws-load-balancer-type: "external"
      service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "ip"
      service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing
      service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp
```
It's only relevant parts, and there are more options to configure.

NLB with NGINX Ingress Controller is overwriting client IP, how to retain actual client IP

Relevant content