-
Notifications
You must be signed in to change notification settings - Fork 466
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
pod networking between the nodes in different subnets #21
Comments
I think we should point this limit(L2 adjacent) out in README.md/requirements section |
@ChenLingPeng thanks, yes you are right it should be in the requirements section. Will add neccessary details. |
I think introducing VXLAN encapsulation for ipvs while preserving source pod IP is the biggest challenge. |
refer to kubernetes/community#692 |
Fixed as part of #92 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current model host gateway based routing of Kube-router assumes nodes are L2 adjacent or in same subnet. this should work fine for most cases. But if we have a cluster with nodes in different subnets, i.e nodes are not in L2 adjacent., then host routing based approach for cross node pod-to-pod connectivity does not work.
Perhaps easy way to address is to use VXLAN encapsulation. So routes are set such that if destination node is in not in same subnet then use the interface to VXLAN encap.
The text was updated successfully, but these errors were encountered: