From 1ef8b37d8d9f6d547a9831c7cdfedb105bea319d Mon Sep 17 00:00:00 2001 From: Michael Schurter Date: Mon, 8 Jul 2019 13:31:07 +0200 Subject: [PATCH] website: minor connect improvements --- .../integrations/consul-connect/index.html.md | 21 ++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/website/source/guides/integrations/consul-connect/index.html.md b/website/source/guides/integrations/consul-connect/index.html.md index 8b5319553..a69c356bf 100644 --- a/website/source/guides/integrations/consul-connect/index.html.md +++ b/website/source/guides/integrations/consul-connect/index.html.md @@ -34,11 +34,11 @@ in Connect continue to work even as the application scales up or down or gets re # Nomad Consul Connect Example The following section walks through an example to enable secure communication -between a web application and a Redis container. The web application and -the Redis container are managed by Nomad. Nomad additionally configures -Envoy proxies to run along side these applications. The web application uses -a localhost port for all Redis communication. The proxy is managed by Nomad, and -handles mTLS communication to the Redis container. +between a web application and a Redis container. The web application and the +Redis container are managed by Nomad. Nomad additionally configures Envoy +proxies to run along side these applications. The web application is configured +to connect to Redis via localhost and Redis's default port (6379). The proxy is +managed by Nomad, and handles mTLS communication to the Redis container. ## Prerequisites @@ -53,8 +53,9 @@ $ consul agent -dev ### Nomad -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. +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 @@ -62,6 +63,12 @@ $ export DEFAULT_IFACE=$(sockaddr eval 'GetAllInterfaces | sort "default" | uniq $ sudo nomad agent -dev -network-interface $DEFAULT_IFACE ``` +Alternatively if you know the network interface Nomad should use: + +```sh +$ sudo nomad agent -dev -network-interface eth0 +``` + ## Run Redis Container Run the following job specification using `nomad run`. This job