From 4f0af55a8f18b159208c244ac5b8f1d1103b6c02 Mon Sep 17 00:00:00 2001 From: Seth Hoenig Date: Tue, 11 Aug 2020 16:43:52 -0500 Subject: [PATCH] docs: update connect integration limitations --- website/pages/docs/integrations/consul-connect.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/website/pages/docs/integrations/consul-connect.mdx b/website/pages/docs/integrations/consul-connect.mdx index 389182538..38cdb4c9a 100644 --- a/website/pages/docs/integrations/consul-connect.mdx +++ b/website/pages/docs/integrations/consul-connect.mdx @@ -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 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 ([#6459][gh6459]). Changing a `meta` variable is the suggested workaround as 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 [gh6120]: https://github.com/hashicorp/nomad/issues/6120