Currently the ingress controller does not forward X-Forwarded-For header values to the upstream service, meaning our miniboard NGINX nor App neither get the real public IP of the connecting client.
Configuring NGINX ingress via ConfigMap resource should allow us to pass the X-Forwarded-For header properly to upstream.
Currently the ingress controller does not forward X-Forwarded-For header values to the upstream service, meaning our miniboard NGINX nor App neither get the real public IP of the connecting client.
Configuring NGINX ingress via ConfigMap resource should allow us to pass the X-Forwarded-For header properly to upstream.