mirror of https://github.com/status-im/consul.git
Merge pull request #10219 from hashicorp/dnephin/connect-docs
docs: update notice on connect built-in proxy and native app integration
This commit is contained in:
parent
29d229ceea
commit
3c8a1b34fa
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in New Issue