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

docs: may->will after confirming with Consul 

Consul 1.9 switched to agentless intentions which no longer require
synchronous communication from Envoy to Consul.
This commit is contained in:
Michael Schurter 2020-12-03 13:48:06 -08:00
parent e948e0a012
commit eb56a75bdd
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/pages/docs/integrations/consul-connect.mdx
View File

@ -329,8 +329,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.
- Consul Connect using network namespaces is only supported on Linux.
- Prior to Nomad 1.0 and Consul 1.9, the Envoy sidecar proxy may drop and stop
accepting connections while the Nomad agent is restarting.
- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
connections while the Nomad agent is restarting.
[count-dashboard]: /img/count-dashboard.png
[gh6120]: https://github.com/hashicorp/nomad/issues/6120

2
website/pages/docs/upgrade/upgrade-specific.mdx
View File

@ -91,7 +91,7 @@ ideal upgrade path is:
3. [Drain][drain-cli] and shutdown old Nomad client nodes.
While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
Envoy proxies may drop and stop accepting connections while the Nomad agent is
Envoy proxies will drop and stop accepting connections while the Nomad agent is
restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
#### Envoy proxy versions