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
d47006d27e
commit
415e4a5012
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 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
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      website/content/docs/upgrading/upgrade-specific.mdx

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

@ -71,7 +71,7 @@ In environments where Envoy proxies are not already configured
to use TLS for gRPC, upgrading to Consul 1.13.0 - 1.13.1 will cause
Envoy proxies to disconnect from the control plane (Consul agents).
If upgrading to version 1.13.2 you must also enable
If upgrading to version 1.13.2 or later, you must enable
[tls.grpc.use_auto_cert](/docs/agent/config/config-files#use_auto_cert)
if you currently use the Connect CA and auto-encrypt certs for TLS
on the gRPC port, and do not have certificates configured via

Write Preview
Loading…
Cancel
Save