website: clarify removal for managed proxies (#5849)

We didn't end up removing these completely in 1.5.0. See also #5848.
This commit is contained in:
Jack Pearkes 2019-05-16 04:48:32 -07:00 committed by Paul Banks
parent b15cb60851
commit 45cdc80767
1 changed files with 2 additions and 2 deletions

View File

@ -22,7 +22,7 @@ recommended you do not build anything using Managed proxies and consider using
registrations](/docs/connect/proxies/sidecar-service.html) instead. registrations](/docs/connect/proxies/sidecar-service.html) instead.
Even though this was a beta feature, managed proxies will continue to work at 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 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 though should aim to change their workflow as soon as possible to avoid issues
with a later upgrade. 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 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 [`-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 configured, this will also cause proxy processes to stay running when the agent
terminates as described in [Lifecycle](#lifecycle). terminates as described in [Lifecycle](#lifecycle).