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
Yup, see #160. kube-router and metallb are known to be incompatible, because of cloudnativelabs/kube-router#242 . MetalLB relies on kube-proxy (or its equivalent) to program the dataplane on every node, and kube-router currently does not. There's nothing I can really do about this, other than wait for kube-router to support loadBalancer endpoints.
@danderson thanks for your prompt response. I noticed as well, that kube-proxy can not work with metallb in ipvs mode. I tried ARP mode and kube-proxy in iptables mode and it works. Switching to ipvs breaks connectivity. Possibly because iptables does DNAT on prerouting stage when ipvs requires packet to be accepted by kernel
Is this a bug report or a feature request?:
More likely a feature
What happened:
MetalLb works perfect with kube-proxy but not with kube-router
What you expected to happen:
It is possibly a kube-router issue, but I expected load balancer just work
How to reproduce it (as minimally and precisely as possible):
Flush your iptables rules, stop kube-proxy, substitute it with kube-router
The text was updated successfully, but these errors were encountered: