aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlex Auvolat <alex@adnab.me>2020-05-23 17:44:49 +0200
committerAlex Auvolat <alex@adnab.me>2020-07-15 16:03:51 +0200
commitd3ada90d83acdbdec38b89c1b039ff07878f5b7d (patch)
treece56929906ee8be99cf4ca44a82e0954d9486b97
parent3bf830713f95c89caf736fa144f90ba7b6b8147a (diff)
downloadinfrastructure-d3ada90d83acdbdec38b89c1b039ff07878f5b7d.tar.gz
infrastructure-d3ada90d83acdbdec38b89c1b039ff07878f5b7d.zip
Fix nomad ip address
Remove the networ_interface parameter in nomad config This means that nomad will now autodetect its own ip address by looking at the default route. Thus nodes in a LAN behind a NAT will get their LAN address, and internet nodes will get their public address. They won't get their VPN addresses. This seems not to break Consul's use of VPN addresses to address services, and fixes attr.unique.network.ip-address for DiploNAT.
-rw-r--r--ansible/roles/nomad/templates/nomad.hcl.j22
1 files changed, 1 insertions, 1 deletions
diff --git a/ansible/roles/nomad/templates/nomad.hcl.j2 b/ansible/roles/nomad/templates/nomad.hcl.j2
index b39a96b..c7a8b94 100644
--- a/ansible/roles/nomad/templates/nomad.hcl.j2
+++ b/ansible/roles/nomad/templates/nomad.hcl.j2
@@ -31,6 +31,6 @@ client {
docker.privileged.enabled = "true"
docker.volumes.enabled = "true"
}
- network_interface = "wgdeuxfleurs"
+ #network_interface = "wgdeuxfleurs"
}