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

docs: update connect integration limitations

Browse source
This commit is contained in:
Seth Hoenig 2020-08-11 16:43:52 -05:00
parent 8d8177e9c2
commit 4f0af55a8f
1 changed files with 1 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
website/pages/docs/integrations/consul-connect.mdx
View file

@ -328,13 +328,10 @@ dashes (`-`) are converted to underscores (`_`) in environment variables so
- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy - The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
proxy sidecar on client nodes. proxy sidecar on client nodes.
- Consul Connect Native requires host networking.
- Only the Docker, `exec`, `raw_exec`, and `java` drivers support network namespaces
and Connect.
- Changes to the `connect` stanza may not properly trigger a job update - Changes to the `connect` stanza may not properly trigger a job update
([#6459][gh6459]). Changing a `meta` variable is the suggested workaround as ([#6459][gh6459]). Changing a `meta` variable is the suggested workaround as
this will always cause an update to occur. this will always cause an update to occur.
- Consul Connect and network namespaces are only supported on Linux. - Consul Connect using network namespaces is only supported on Linux.
[count-dashboard]: /img/count-dashboard.png [count-dashboard]: /img/count-dashboard.png
[gh6120]: https://github.com/hashicorp/nomad/issues/6120 [gh6120]: https://github.com/hashicorp/nomad/issues/6120