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
The ingress routing mesh loses the client source IP, and some web apps need this. This enhancement would add an example/option for placing traefik on --network host so it can capture those source IP's and send them as host headers to backend services on an overlay network.
With traefik this makes the whole thing a bit more complex because we now must have a traefik replica on every node (global mode) which means we can't cheat with the TOML config file and cert files like we can with a single-replica traefik service. We'll need a config backend for traefik to make this work.
The text was updated successfully, but these errors were encountered:
The ingress routing mesh loses the client source IP, and some web apps need this. This enhancement would add an example/option for placing traefik on
--network host
so it can capture those source IP's and send them as host headers to backend services on an overlay network.With traefik this makes the whole thing a bit more complex because we now must have a traefik replica on every node (global mode) which means we can't cheat with the TOML config file and cert files like we can with a single-replica traefik service. We'll need a config backend for traefik to make this work.
The text was updated successfully, but these errors were encountered: