From 6127421eab378f29d64acd88e751448024c727de Mon Sep 17 00:00:00 2001 From: Freddy Date: Fri, 21 Oct 2022 15:15:22 -0600 Subject: [PATCH] Update website/content/docs/upgrading/upgrade-specific.mdx Co-authored-by: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com> --- website/content/docs/upgrading/upgrade-specific.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/content/docs/upgrading/upgrade-specific.mdx b/website/content/docs/upgrading/upgrade-specific.mdx index 140f5e7ab..33d75e8a9 100644 --- a/website/content/docs/upgrading/upgrade-specific.mdx +++ b/website/content/docs/upgrading/upgrade-specific.mdx @@ -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 -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 to require TLS for gRPC communication with Envoy proxies.