Dynamic port range should be configurable in client config

[evandam]

Similar to #7399 and #1087, it would be helpful to set the range Nomad uses for dynamic ports, but on the client level instead of the job/task.

I see there's reserved_ports that can be set, but that still relies on the hard-coded range of 20k-32k. For example, there's no way to shift the dynamic port range from 20000-32000 to 32000-44000.

I'm also unsure if #3072 would still pose an issue with setting large reserved_port ranges.

[tgross]

This looks like a reasonable request and one we've wanted to do for a while. There's an open PR in #8478 from @prestonp that is a good first attempt. If that gets fixed up I think we'll be good to get this in.

[insanitybit]

I think ideally I would be able to do this task-level. I'd like to set up some iptables and monitoring that can rely on specific port ranges being allocated to specific tasks.

[a-zagaevskiy]

I've already had a working code, initially based on the mentioned PR #8478, which takes into account recommendations about spreading client's dynamic port range via fingerprints. And it works quite well. But it fixes Nomad v0.10.6. I could try to rebase it on the current master, if you are interested.

[Oloremo]

Waiting for that feature as well

[jrasell]

This functionality was added within #11167 and will be released in Nomad 1.2.0.

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