Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NGINX Ingress Controller is the source of all traffic in NGINX logs #512

Open
kierenevans opened this issue Dec 23, 2020 · 0 comments
Open
Labels
bug Something isn't working
Milestone

Comments

@kierenevans
Copy link
Contributor

We need to enable the realip module and filter X-Forwarded-For to remove the NGINX ingress controller pod's IP.

Alternatively we might be able to get the NGINX Ingress controller to forward the real IP directly, though if varnish is in the middle we have the same problem.

Might make sense to have this configurable via attributes.

This will ensure applications know the client's IP address for fraud checks, etc.

@kierenevans kierenevans added the bug Something isn't working label Dec 23, 2020
@kierenevans kierenevans added this to the 0.12.0 milestone Dec 23, 2020
@kierenevans kierenevans modified the milestones: 0.12.0, 0.13.0, 1.1.0 Jan 6, 2021
@kierenevans kierenevans modified the milestones: 1.1.0, 1.2.0 Mar 9, 2021
@kierenevans kierenevans modified the milestones: 1.2.0, 1.3.0 Dec 10, 2021
@andytson-inviqa andytson-inviqa modified the milestones: 1.3.0, 1.4.0 Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants