website: minor connect improvements

This commit is contained in:
Michael Schurter 2019-07-08 13:31:07 +02:00
parent c6064c663a
commit 1ef8b37d8d
1 changed files with 14 additions and 7 deletions

View File

@ -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