If you set externalTrafficPolicy: Local, MetalLB itself is doing the
work to make original source IPs work. However, the component that
actually changes or preserves the source IP is not MetalLB, it's
kube-proxy combined with whatever network addon you use. If you set
externalTrafficPolicy=Local and your traffic is still being NATed,
it's a bug in either upstream Kubernetes (kube-proxy), or in your
network addon.
- Dave
> --
> You received this message because you are subscribed to the Google Groups "metallb-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
metallb-user...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/metallb-users/2005b222-fa6a-45d0-bab3-a7ffd28395f8%40googlegroups.com.