-
Notifications
You must be signed in to change notification settings - Fork 600
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
Is there a way to communicate across kubernetes nodes? #7
Comments
Why can't you use flannel Multiple Network use case ? It is more efficient than using ptp plugin. |
Actually, I'd like to use flannel Multiple network. |
If I understand well, the conf should be like
Am I right? |
Please follow the steps for the Mutliple flannel Network. To my knowledge ipam is not allowed in flannel delegate, please correct me if I am wrong. Flannel get the IPAM information from the |
@YYGCui - Is the Multiple Flannel Network, solved your issue ? |
Multiple Flannel Network is worked for me. Thanks! the conf file
|
@YYGCui added your CNI config information in the Multus README.md file |
I use flannel to communicate across kubernetes nodes. pods can communicate via the default interface eth0.
If I add more one, the cni configure file looks as follows:
---master---
---minion---
the pods in the same node can reachable, but across nodes unreachable because they are in different subnets.(use different subnets to avoid ip conflict)
I cannot find a way to make them reachable.
should I use the default route? (created by flannel-docker-bridge)
Is there are some example for that?
The text was updated successfully, but these errors were encountered: