Replies: 2 comments 2 replies
-
@BenB196 can you share the Traefik logs? I'd start off with this by figuring out which value Traefik is using to log the IPs. Because the proxy is injected into the container and is handling requests for Traefik, it is technically coming from 127.0.0.1, so it would help to look at the headers that Traefik receives to find out if the IP address is in any of those headers like |
Beta Was this translation helpful? Give feedback.
2 replies
-
Support for |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All,
I am trying to use linkerd with traefik and am running into a issue, where is I inject traefik with
ingress
, it causes all IPs in traefik logs to show up as 127.0.0.1. If I un-inject linkerd from traefik I see the client IPs in the traefik logs again.I've also tried injecting linkerd via
enabled
as well and got the same issue.I believe this is either an issue with how linkerd/traefik interacts, because if I replace traefik with nginx, everything works fine.
Any help on this would be greatly appreciated as I've been stuck on this issue for a while now.
See below for deployment specific stuff.
Linkerd - 2.10.0
Traefik - 2.4.8
Traefik deployed via Helm:
Linkerd deployed via cli:
Using Metallb to provide the LoadBalancer IP
Testing using the linkerd-viz web.
Beta Was this translation helpful? Give feedback.
All reactions