status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update website/content/docs/upgrading/upgrade-specific.mdx 

Co-authored-by: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com>
This commit is contained in:
Freddy 2022-10-21 15:15:29 -06:00 committed by GitHub
parent 8c6a8f0b28
commit 5944c28dd6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/upgrading/upgrade-specific.mdx
View File

@ -65,7 +65,7 @@ Upgrade to **Consul version 1.13.2 or later** if using
[auto-encrypt](/docs/agent/config/config-files#auto_encrypt) or [auto-encrypt](/docs/agent/config/config-files#auto_encrypt) or
[auto-config](/docs/agent/config/config-files#auto_config). [auto-config](/docs/agent/config/config-files#auto_config).
In Consul 1.13.1, auto-encrypt and auto-config both cause Consul In Consul 1.13.0 - 1.13.1, auto-encrypt and auto-config both cause Consul
to require TLS for gRPC communication with Envoy proxies. to require TLS for gRPC communication with Envoy proxies.
In environments where Envoy proxies are not already configured In environments where Envoy proxies are not already configured
to use TLS for gRPC, upgrading Consul 1.13.1 will cause to use TLS for gRPC, upgrading Consul 1.13.1 will cause