-
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
Nomad doesn't respect Consuls "translate_wan_addrs" #3629
Comments
This is also true for vault, would you like me to duplicate the issue there? |
@perrymanuk If you don't mind. Please drop a link from one to other as well. |
I see this as well from Nomad v0.8.6. |
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. |
Nomad version
Output from
0.7.0
Operating system and Environment details
Debian 9
Issue
Consul is configured to translate wan addresses, this works perfectly for the nomad nodes and for services announced directly to consul. However the same is not true for the services announced to consul by nomad.
Reproduction steps
ping nomad-node-name.service.datacenter.consul
ping service-running-in-nomad.service.datacenter.consul
The text was updated successfully, but these errors were encountered: