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

update docs and add changelog

This commit is contained in:
woz5999 2020-08-25 15:19:42 -07:00 committed by Daniel Nephin
parent 1585ea3734
commit e05877e633
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
.changelog/8564.txt Normal file
View File

@ -0,0 +1,3 @@
```release-notes:improvement
cli: the `consul connect envoy --envoy_statsd_url` flag will now resolve the `$HOST_IP` environment variable, as part of a full url.
```

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

@ -130,15 +130,17 @@ definition](/docs/connect/registration/service-registration) or
~> **Note:** currently the url **must use an ip address** not a dns name due ~> **Note:** currently the url **must use an ip address** not a dns name due
to the way Envoy is setup for StatsD. to the way Envoy is setup for StatsD.
Expansion of the environment variable `HOST_IP` is supported, e.g.
`udp://${HOST_IP}:8125`.
Users can also specify the whole parameter in the form `$ENV_VAR_NAME`, which Users can also specify the whole parameter in the form `$ENV_VAR_NAME`, which
will cause the `consul connect envoy` command to resolve the actual URL from will cause the `consul connect envoy` command to resolve the actual URL from
the named environment variable when it runs. This, for example, allows each the named environment variable when it runs. This, for example, allows each
pod in a Kubernetes cluster to learn of a pod-specific IP address for StatsD pod in a Kubernetes cluster to learn of a pod-specific IP address for StatsD
when the Envoy instance is bootstrapped while still allowing global when the Envoy instance is bootstrapped while still allowing global
configuration of all proxies to use StatsD in the [global `proxy-defaults` configuration of all proxies to use StatsD in the [global `proxy-defaults`
configuration entry](/docs/connect/config-entries/proxy-defaults). The env variable must contain a full valid URL configuration entry](/docs/connect/config-entries/proxy-defaults). The env
value as specified above and nothing else. It is not currently possible to use variable must contain a full valid URL value as specified above and nothing else.
environment variables as only part of the URL.
- `envoy_dogstatsd_url` - The same as `envoy_statsd_url` with the following - `envoy_dogstatsd_url` - The same as `envoy_statsd_url` with the following
differences in behavior: differences in behavior: