luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

website: change consul and nomad start up to reflect changes

This commit is contained in:
Nick Ethier 2019-07-07 06:07:26 -04:00
parent 1206c895f6
commit c6064c663a
No known key found for this signature in database
GPG Key ID: 07C1A3ECED90D24A
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
website/source/guides/integrations/consul-connect/index.html.md
View File

@ -44,19 +44,17 @@ handles mTLS communication to the Redis container.
### Consul
Connect requires Consul 1.6 (TODO Download link). Consul must advertise on a routable
address. The following steps show how to start a Consul dev agent configured for Connect.
Connect integration with Nomad requires Consul 1.6 (TODO Download link). The
Consul agent can be ran in dev mode with the following command:
```sh
$ go get -u github.com/hashicorp/go-sockaddr/cmd/sockaddr
$ export DEFAULT_IP=$(sockaddr eval GetAllInterfaces | sort "default" | exclude "type" "IPv6" | limit 1 | attr "address")
$ consul agent -dev -bind 0.0.0.0 -client 192.168.86.27 -advertise 192.168.86.27
$ consul agent -dev
```
### Nomad
Nomad must also schedule onto a routable interface. The following steps show how to start
a Nomad dev agent configured for Connect.
Nomad must schedule onto a routable interface in order for the proxies to connect
to each other. The following steps show how to start a Nomad dev agent configured for Connect.
```sh
$ go get -u github.com/hashicorp/go-sockaddr/cmd/sockaddr
@ -166,4 +164,4 @@ job "api" {
After running this job, visit the Nomad UI to see the Envoy proxies managed by Nomad
both for the web application and its upstream Redis service. The Consul UI also shows
the registered Connect proxies.
the registered Connect proxies.