minor corrections

* hcl formatting
* demo is on localhost not host ip
* clarify consul on PATH
This commit is contained in:
Michael Schurter 2019-09-05 08:56:39 -07:00
parent e866e92ff4
commit 58f13da372
1 changed files with 9 additions and 7 deletions

View File

@ -48,7 +48,7 @@ Connect integration with Nomad requires [Consul 1.6 or
later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
run in dev mode with the following command: run in dev mode with the following command:
**Note**: for this demo to work, Consul must be in your $PATH **Note**: Nomad's Connect integration requires Consul in your `$PATH`
```sh ```sh
$ consul agent -dev $ consul agent -dev
@ -211,7 +211,7 @@ a host network interface. The `to = 9002` parameter forwards that host port to
port 9002 inside the network namespace. port 9002 inside the network namespace.
This allows you to connect to the web frontend in a browser by visiting This allows you to connect to the web frontend in a browser by visiting
`http://<host_ip>:9002` as show below: http://127.0.0.1:9002 as show below:
[![Count Dashboard][count-dashboard]][count-dashboard] [![Count Dashboard][count-dashboard]][count-dashboard]
@ -254,9 +254,11 @@ dashes (`-`) are converted to underscores (`_`) in environment variables so
## Limitations ## Limitations
- Consul Connect Native is not yet supported - The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
- Consul Connect HTTP and gRPC checks are not yet supported proxy sidecar on client nodes.
- Consul ACLs are not yet supported - Consul Connect Native is not yet supported.
- Consul Connect HTTP and gRPC checks are not yet supported.
- Consul ACLs are not yet supported.
- Only the Docker, exec, and raw exec drivers support network namespaces and - Only the Docker, exec, and raw exec drivers support network namespaces and
Connect. Connect.