Clients working behind NAT

[sheerun]

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?

[dadgar]

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

[sheerun]

@dadgar Could you test and document network connectivity requirements on https://www.nomadproject.io/docs/cluster/requirements.html ?

[sheerun]

@dadgar It seems client need public ip address for nomad logs command to work.. So they aren't working properly behind a NAT. Am I wrong? Could nomad implement something like https://github.com/fatedier/frp ?

[dadgar]

@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.

[sheerun]

@dadgar What about RPC?

[dadgar]

RPC should work because clients dial the servers not the other way.

[dadgar]

Solved by #3892

[github-actions]

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.