From 45cdc8076703212b6ff3e31b50f226fbbef5ef7c Mon Sep 17 00:00:00 2001 From: Jack Pearkes Date: Thu, 16 May 2019 04:48:32 -0700 Subject: [PATCH] website: clarify removal for managed proxies (#5849) We didn't end up removing these completely in 1.5.0. See also #5848. --- .../source/docs/connect/proxies/managed-deprecated.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/connect/proxies/managed-deprecated.html.md b/website/source/docs/connect/proxies/managed-deprecated.html.md index 6a52bb7e74..de3042c40f 100644 --- a/website/source/docs/connect/proxies/managed-deprecated.html.md +++ b/website/source/docs/connect/proxies/managed-deprecated.html.md @@ -22,7 +22,7 @@ recommended you do not build anything using Managed proxies and consider using registrations](/docs/connect/proxies/sidecar-service.html) instead. Even though this was a beta feature, managed proxies will continue to work at -least until Consul 1.5 to prevent disruption to demonstration and +least until Consul 1.6 to prevent disruption to demonstration and proof-of-concept deployments of Consul Connect. Anyone using managed proxies though should aim to change their workflow as soon as possible to avoid issues with a later upgrade. @@ -281,4 +281,4 @@ level logs showing service discovery, certificate and authorization information. configured so logging is disabled. You can access logs by providing the [`-data-dir`](/docs/agent/options.html#_data_dir) CLI option. If a data dir is configured, this will also cause proxy processes to stay running when the agent -terminates as described in [Lifecycle](#lifecycle). \ No newline at end of file +terminates as described in [Lifecycle](#lifecycle).