Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not make MetalLB work with kube-router #164

Closed
vladimirtiukhtin opened this issue Feb 16, 2018 · 3 comments
Closed

Can not make MetalLB work with kube-router #164

vladimirtiukhtin opened this issue Feb 16, 2018 · 3 comments

Comments

@vladimirtiukhtin
Copy link

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

@danderson
Copy link
Contributor

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.

@vladimirtiukhtin
Copy link
Author

@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

@danderson
Copy link
Contributor

Yup, that's #153. I haven't had time to diagnose it yet, but I suspect IPVS mode in kube-proxy might also be ignoring LoadBalancer IPs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants