interpolate network.dns block on client #11851
Labels
stage/accepted
Confirmed, and intend to work on. No timeline committment though.
theme/networking
type/enhancement
Milestone
Comments
tgross
added
the
stage/accepted
nvx
added a commit
to nvx/nomad
that referenced
this issue
Feb 8, 2022
|
#12021 has been merged and will ship in 1.3.0 |
ghost
pushed a commit
to grapl-security/grapl
that referenced
this issue
Apr 10, 2022
With the move of dnsmasq to the host, we now need a way to tell the containers to use the host for their dns lookups if they want to use consul dns. Typically on a host you would just add a nameserver for 127.0.0.1, but that doesn't work because in the container 127.0.0.1 points to the container not the host. Ideally we'd just be passing in attr.unique.network.ip-address, but unfortunately, variable interpolation is only available for network.dns as of Nomad 1.3 per hashicorp/nomad#11851 So instead we're stuck doing grabbing an IP from `hostname -I` and passing that in as an environment variable. This may actually be for the best if we end up setting a distinct dns service in production
inickles-grapl
pushed a commit
to grapl-security/grapl
that referenced
this issue
Apr 20, 2022
With the move of dnsmasq to the host, we now need a way to tell the containers to use the host for their dns lookups if they want to use consul dns. Typically on a host you would just add a nameserver for 127.0.0.1, but that doesn't work because in the container 127.0.0.1 points to the container not the host. Ideally we'd just be passing in attr.unique.network.ip-address, but unfortunately, variable interpolation is only available for network.dns as of Nomad 1.3 per hashicorp/nomad#11851 So instead we're stuck doing grabbing an IP from `hostname -I` and passing that in as an environment variable. This may actually be for the best if we end up setting a distinct dns service in production
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From #11845 (comment) @nvx requested being able to interpolate the
network.dns.serversfield with node metadata. We likely don't interpolate thenetworkblock because we need it to be complete for scheduling, but thednsblock defaults to the client if unset, so it should be safe to interpolate after landing on the client.The text was updated successfully, but these errors were encountered: