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

docs: clarify envoy proxy configuration (#15562) 

- Specify using the service config entry to configure
  service's envoy proxy
- add missing fields in proxy.config
This commit is contained in:
cskh 2022-11-28 20:33:54 -05:00 committed by GitHub
parent 90ca02b70d
commit a070840dc7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
website/content/docs/connect/proxies/envoy.mdx
View File

@ -253,11 +253,12 @@ $ envoy -c bootstrap.json
Consul automatically generates Envoy's dynamic configuration based on its Consul automatically generates Envoy's dynamic configuration based on its
knowledge of the cluster. Users may specify default configuration options for knowledge of the cluster. Users may specify default configuration options for
each service such as which protocol they speak. Consul will use this information a service through the available fields in the [`service-defaults` configuration
to configure appropriate proxy settings for that service's proxies and also for entry](/docs/connect/config-entries/service-defaults). Consul will use this
the upstream listeners of any downstream service. information to configure appropriate proxy settings for that service's proxies
and also for the upstream listeners used by the service.
One example is how users can define a service's protocol in a [`service-defaults` configuration One example is how users can define a service's protocol in the `Protocol` field of [`service-defaults` configuration
entry](/docs/connect/config-entries/service-defaults). Agents with entry](/docs/connect/config-entries/service-defaults). Agents with
[`enable_central_service_config`](/docs/agent/config/config-files#enable_central_service_config) [`enable_central_service_config`](/docs/agent/config/config-files#enable_central_service_config)
set to true will automatically discover the protocol when configuring a proxy set to true will automatically discover the protocol when configuring a proxy
@ -276,7 +277,7 @@ To learn about other options that can be configured centrally see the
### Proxy Config Options ### Proxy Config Options
These fields may also be overridden explicitly in the [proxy service These fields may also be overridden explicitly in `proxy.config` of the [proxy service
definition](/docs/connect/registration/service-registration), or defined in definition](/docs/connect/registration/service-registration), or defined in
the [global `proxy-defaults` configuration the [global `proxy-defaults` configuration
entry](/docs/connect/config-entries/proxy-defaults) to act as entry](/docs/connect/config-entries/proxy-defaults) to act as
@ -329,6 +330,9 @@ defaults that are inherited by all services.
specified, inherits the Envoy default for route timeouts (15s). A value of 0 will specified, inherits the Envoy default for route timeouts (15s). A value of 0 will
disable request timeouts. disable request timeouts.
- `max_inbound_connections` - The maximum number of concurrent inbound connections
to the local application instance. If not specified, inherits the Envoy default (1024).
- `balance_inbound_connections` - The strategy used for balancing inbound connections - `balance_inbound_connections` - The strategy used for balancing inbound connections
across Envoy worker threads. Consul service mesh Envoy integration supports the across Envoy worker threads. Consul service mesh Envoy integration supports the
following `balance_inbound_connections` values: following `balance_inbound_connections` values: