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
It thinks I logged in from the IP address 10.0.0.118, which happens to be star4, where the nginx ingress is running. Ideally, we want to expose the client's IP address for logging purposes (and maybe to blacklist certain IP ranges in the future if we see abuse of our servies).
Apparantly this is an issue on Flock as well, even if we aren't using an ingress (but that's because it runs autohttps (traefik) to deal with https traffic, which acts like an ingress anyway):
When testing something on Galaxy I saw stuff like:
It thinks I logged in from the IP address 10.0.0.118, which happens to be star4, where the nginx ingress is running. Ideally, we want to expose the client's IP address for logging purposes (and maybe to blacklist certain IP ranges in the future if we see abuse of our servies).
Apparantly this is an issue on Flock as well, even if we aren't using an ingress (but that's because it runs autohttps (traefik) to deal with https traffic, which acts like an ingress anyway):
See also: kubernetes/ingress-nginx#6163
The text was updated successfully, but these errors were encountered: