You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In user-defined networks the --network-alias can be useful to manage service discovery within e.g. Docker overlay networks. Two containers having the same Network Alias results in multiple addresses listed under that alias.
E.g. a scheme we have currently under Nomad 0.4.0 (done by building our own raw_exec-based driver) is to give each container four aliases like this:
such that we can easily route traffic to any single container, or to a random container in a task or group. (The last alias is not particularly useful for service discovery, but is required so that DNS queries resolve for its subdomains.)
Nomad 0.5.0-rc1 has all the features we need to drop our custom driver, except support for Docker network aliases. I acknowledge that it is probably too late for this to be included in 0.5.0, but we can workaround. Nevertheless, it would be a useful feature.
The text was updated successfully, but these errors were encountered:
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.
In user-defined networks the
--network-alias
can be useful to manage service discovery within e.g. Docker overlay networks. Two containers having the same Network Alias results in multiple addresses listed under that alias.E.g. a scheme we have currently under Nomad 0.4.0 (done by building our own
raw_exec
-based driver) is to give each container four aliases like this:such that we can easily route traffic to any single container, or to a random container in a task or group. (The last alias is not particularly useful for service discovery, but is required so that DNS queries resolve for its subdomains.)
Nomad 0.5.0-rc1 has all the features we need to drop our custom driver, except support for Docker network aliases. I acknowledge that it is probably too late for this to be included in 0.5.0, but we can workaround. Nevertheless, it would be a useful feature.
The text was updated successfully, but these errors were encountered: