-
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
Dynamic port range should be configurable in client config #8186
Comments
The intent of this change is to support shifting the range used for assigning dynamic ports (hashicorp#8186). This makes the static dynamic port range configurable per new client settings `dynamic_port_range_min` and `dynamic_port_range_max`.
The intent of this change is to support shifting the range used for assigning dynamic ports (hashicorp#8186). This makes the static dynamic port range configurable per new client settings `dynamic_port_range_min` and `dynamic_port_range_max`.
The intent of this change is to support shifting the range used for assigning dynamic ports (hashicorp#8186). This makes the static dynamic port range configurable per new client settings `dynamic_port_range_min` and `dynamic_port_range_max`.
The intent of this change is to support shifting the range used for assigning dynamic ports (hashicorp#8186). This makes the static dynamic port range configurable per new client settings `dynamic_port_range_min` and `dynamic_port_range_max`.Fix port range to server config
The intent of this change is to support shifting the range used for assigning dynamic ports (hashicorp#8186). This makes the static dynamic port range configurable per new server settings `dynamic_port_range_min` and `dynamic_port_range_max`.
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. |
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. |
Waiting for that feature as well |
The intent of this change is to support shifting the range used for assigning dynamic ports (hashicorp#8186). This makes the static dynamic port range configurable per new server settings `dynamic_port_range_min` and `dynamic_port_range_max`.
This functionality was added within #11167 and will be released in Nomad 1.2.0. |
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. |
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 from20000-32000
to32000-44000
.I'm also unsure if #3072 would still pose an issue with setting large reserved_port ranges.
The text was updated successfully, but these errors were encountered: