-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Fix multi-interface networking in the system scheduler #8822
Fix multi-interface networking in the system scheduler #8822
Conversation
Thank you very much for this contribution. Any chance you can add a test as well? |
I may not have the bandwidth to test this fully, as I don't think much of the multi-interface networking code is under coverage at the moment; e.g. we are also seeing issues with multi-interface IP assignment in Consul service registrations (which we have patched in our fork). But I'm very much willing to collaborate on the effort to wrangle these bugs. |
Thanks @neilmock I'll take on trying to get this tested a bit better. I'd love to hear more about any other patches you've made wrt multi-interface IP networking. |
We haven't done much, but we did put in a hack to make Consul register the correct host IP/interface for services. You can see a diff here. |
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
This was originally mentioned in #8208 (comment), and purportedly fixed in #8230, but we noticed our system job appeared to bind on all interfaces instead of the specified
host_network
.We noticed we were always evaluating to the first half of this conditional which didn't seem right:
nomad/client/allocrunner/networking_cni.go
Line 170 in 4ba3afa
This is a proposed fix, it seems correct given previous discussion but we are new to Nomad internals.