Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Deprecations for connect-native SDK and specific connect native APIs #17937

Merged
merged 21 commits into from
Jun 28, 2023
Prev Previous commit
Next Next commit
Update integrate.mdx
  • Loading branch information
David Yu authored Jun 28, 2023
commit 7f541fffaabb377de97e13b20e8052b9573643df
8 changes: 8 additions & 0 deletions website/content/docs/connect/proxies/integrate.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down