You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.
We are trying to apply some Deny rules on our Ingress, however, in our logs in our pods, and from the Ingress Controller Pods themselves it seems that ALL traffic to them is coming from one of the NMI Pods and the true Client IP is never reaching in.
Is this how it is supposed to be behaving this way, it seems weird that even our Ingress Pods are seeing the NMI IPs and not the clients as I would expect all traffic to hit NGINX first?
Is there a setting we are missing to have the true Client IP forwarded or prevent NMI from (what seems to be) intercepting ingress traffic?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are trying to apply some Deny rules on our Ingress, however, in our logs in our pods, and from the Ingress Controller Pods themselves it seems that ALL traffic to them is coming from one of the NMI Pods and the true Client IP is never reaching in.
Is this how it is supposed to be behaving this way, it seems weird that even our Ingress Pods are seeing the NMI IPs and not the clients as I would expect all traffic to hit NGINX first?
Is there a setting we are missing to have the true Client IP forwarded or prevent NMI from (what seems to be) intercepting ingress traffic?
Beta Was this translation helpful? Give feedback.
All reactions