From 217902cf9eb8ea497bde0c5afdcb2cc58723a0e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jos=C3=A9=20Maia?= Date: Tue, 20 Oct 2020 15:32:41 +0100 Subject: [PATCH] Remove limitation that has been fixed Issue #6459 has been fixed for a while, but the docs still point to it as a limitation --- website/pages/docs/integrations/consul-connect.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/website/pages/docs/integrations/consul-connect.mdx b/website/pages/docs/integrations/consul-connect.mdx index 1d13357844a..69a2cda35bc 100644 --- a/website/pages/docs/integrations/consul-connect.mdx +++ b/website/pages/docs/integrations/consul-connect.mdx @@ -328,12 +328,8 @@ 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. -- 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 using network namespaces is only supported on Linux. [count-dashboard]: /img/count-dashboard.png [gh6120]: https://github.com/hashicorp/nomad/issues/6120 [gh6701]: https://github.com/hashicorp/nomad/issues/6701 -[gh6459]: https://github.com/hashicorp/nomad/issues/6459