-
Notifications
You must be signed in to change notification settings - Fork 58
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
Usernetes with bypass4netns on multi-node #335
Labels
question
Further information is requested
Comments
I didn't read the entire note yet, but etcd is not needed for multi-node. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @AkihiroSuda ! 👋
I want to introduce you to @lisejolicoeur, who has joined our team this summer (with @milroy) to work specifically on Usernetes networking! We are opening this issue to share our progress, and ask for your expertise for next steps to try.
Specifically, @lisejolicoeur has led us to extend our original setup on AWS to add back bypass4netns with multi-node, and we have taken notes that detail our approach. Lise is leading the work and is experienced with Kubernetes networking, and we are hopeful to start discussion here about next steps we might try. If we work together, we might be able to figure out solutions to some of the current challenges with getting bypass4netns working in this multi-node setup.
Our proposal is that if you might have time, please review our setup, and take note of the points of interest and questions indicated with ❓️. Please feel free to comment on or otherwise edit the document - it is a working space for us! We are at the point where we have a control plane running (without bypass) and two worker nodes (with bypass) and can shell into pods on other nodes, but cannot ping from pod to pod. Please let us know if you see anything that sticks out, and what we might try next.
Thank you, and happy weekend! 🥳
The text was updated successfully, but these errors were encountered: