Nomad: Service registration with fqdn rather than ip address
While registering services with nomad, service address is always set to ip of the service.
It would be very handy if there is an option to register services with fully qualified domain names especially when there is a proxy in the environment.
Do you consider adding such an option in the near future?
Nomad version
Output from nomad version
Nomad v0.5.2-rc1
turkenh
All 2 comments
+1 we so need this. Right now the auto-registry feature with IPs is broken for us since we need proper hostnames for TLS and stuff. A configurable template for what should be used to register a service from a specific node would solve this nicely.
There are very similar requests to this:
https://github.com/hashicorp/nomad/issues/2770
https://github.com/hashicorp/nomad/issues/4815
derzufall
on 26 Aug 2019
We also need to register Consul services using FQDN by Nomad because we want to use HTTPS with TLS verify for discovered services.
Also a service healthcheck address should be also configurable and allow us to set FQDN to do an internal consul http check using https://hostname address w/o any InsecureVerify True because it's insecure :)
Currently, we patched Nomad like this https://github.com/Quiq/nomad/commit/a081ee28ad22dc1acc0a8c3fde7b063b7809c4aa
roman-vynar
on 19 Aug 2020
Related issues
stongo
路
3Comments
mancusogmu
路
3Comments
DanielDent
路
3Comments
clinta
路
3Comments
leowmjw
路
3Comments
Most helpful comment
We also need to register Consul services using FQDN by Nomad because we want to use HTTPS with TLS verify for discovered services.
Also a service healthcheck address should be also configurable and allow us to set FQDN to do an internal consul http check using https://hostname address w/o any InsecureVerify True because it's insecure :)
Currently, we patched Nomad like this https://github.com/Quiq/nomad/commit/a081ee28ad22dc1acc0a8c3fde7b063b7809c4aa