luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

docs: document the current state of built-in and native

This commit is contained in:
Daniel Nephin 2021-05-10 16:37:16 -04:00
parent f63f1db498
commit d34ad26b72
2 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/content/docs/connect/native/index.mdx
View File

@ -9,6 +9,11 @@ description: >-
# Connect-Native App Integration
~> **Note:** The Native App Integration does not support many of the Connect service
mesh features, and is not under active development.
The [Envoy proxy](/docs/connect/proxies/envoy) should be used for most production
environments.
Applications can natively integrate with the Connect API to support accepting
and establishing connections to other Connect services without the overhead of a
[proxy sidecar](/docs/connect/proxies). This option is especially useful

9
website/content/docs/connect/proxies/built-in.mdx
View File

@ -6,10 +6,13 @@ description: Consul Connect comes with a built-in proxy for testing and developm
# Built-In Proxy Options
Consul comes with a built-in L4 proxy for testing and development with Consul
Connect.
~> **Note:** The built-in proxy is not supported for production deployments. It does not
support many of the Connect service mesh features, and is not under active development.
The [Envoy proxy](/docs/connect/proxies/envoy) should be used for production deployments.
Consul comes with a built-in L4 proxy for testing and development with Consul
Connect service mesh.
~> **Note:** [Envoy](/docs/connect/proxies/envoy) should be used for production deployments, or when [layer 7 traffic management](/docs/connect/l7-traffic-management) features are needed.
## Getting Started