From 7f541fffaabb377de97e13b20e8052b9573643df Mon Sep 17 00:00:00 2001 From: David Yu Date: Wed, 28 Jun 2023 10:12:42 -0700 Subject: [PATCH] Update integrate.mdx --- website/content/docs/connect/proxies/integrate.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/website/content/docs/connect/proxies/integrate.mdx b/website/content/docs/connect/proxies/integrate.mdx index 1ad9f4b91156..ba72f1c6f075 100644 --- a/website/content/docs/connect/proxies/integrate.mdx +++ b/website/content/docs/connect/proxies/integrate.mdx @@ -7,6 +7,14 @@ description: >- # Custom Proxy Configuration for Service Mesh +~> **Note:** The Native App Integration does not support many of the Consul's service + mesh features, and is not under active development. + The [Envoy proxy](/consul/docs/connect/proxies/envoy) should be used for most production + environments. The Connect Native Golang SDK and `v1/agent/connect/authorize`, `v1/agent/connect/ca/leaf`, + and `v1/agent/connect/ca/roots` APIs are deprecated and will be removed in a future release. Although Connect Native + is still supported we discourage new users from adopting this feature at this time, as we plan to remove the feature + when a future long term replacement such as proxyless GRPC via XDS is delivered (see [GH-10339](https://github.com/hashicorp/consul/issues/10339)). + This topic describes the process and API endpoints you can use to extend proxies for integration with Consul. ## Overview