-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Clients working behind NAT #1640
Comments
Nomad clients dial the Servers and hold long lived TCP connections so I don't think it would be a problem. We can open if it is |
@dadgar Could you test and document network connectivity requirements on https://www.nomadproject.io/docs/cluster/requirements.html ? |
@dadgar It seems client need public ip address for |
@sheerun Nomad logs won't work because the CLI is dialing the agent but it is a NATed connection but the client should be able to run tasks just fine. I am going to re-open this issue and use this to track the use case of enabling proxying for the HTTP endpoints. |
@dadgar What about RPC? |
RPC should work because clients dial the servers not the other way. |
Solved by #3892 |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Last time I checked nomad had issues running worker nodes behind NAT.
My usecase: I'd like nomad servers to run in the cloud, but nomad clients to run on my machine and execute tasks. This is a model that new docker swarm model allows in docker 1.12, but I'd like to nomad without docker installed (many clouds don't allow it, e.g. because there's missing TUN interface, or cgroups is not available).
Is it currently possible to run worker nodes behind NAT?
Are there plans to support it?
The text was updated successfully, but these errors were encountered: