github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

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

Co-authored-by: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com>
pull/15028/head
Freddy 2 years ago committed by GitHub
parent
ef2127ec51
commit
8c6a8f0b28
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 4
      website/content/docs/upgrading/upgrade-specific.mdx

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

@ -61,7 +61,9 @@ This bug is fixed in Consul versions 1.13.1 and newer.
#### Service mesh deployments using auto-encrypt or auto-config #### Service mesh deployments using auto-encrypt or auto-config
Upgrade to **Consul version 1.13.2 or later**. Upgrade to **Consul version 1.13.2 or later** if using
[auto-encrypt](/docs/agent/config/config-files#auto_encrypt) or
[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.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.

Write Preview
Loading…
Cancel
Save