website: note that env vars are set

This commit is contained in:
Mitchell Hashimoto 2018-10-08 09:55:55 -07:00
parent fd46c6d7ce
commit a4abd8dd76
No known key found for this signature in database
GPG Key ID: A3A9A8F4F25C3E56
1 changed files with 8 additions and 0 deletions

View File

@ -113,11 +113,19 @@ port, the proxy establishes a connection to the target service
("static-server" in this example) using ("static-server" in this example) using
mutual TLS and identifying as the source service ("static-client" in this mutual TLS and identifying as the source service ("static-client" in this
example). example).
The injector will also set environment variables `<NAME>_CONNECT_SERVICE_HOST`
and `<NAME>_CONNECT_SERVICE_PORT` for every defined upstream. This is
analogous to the standard Kubernetes service environment variables, but
point instead to the correct local proxy port to establish connections via
Connect.
Any containers running in the pod that need to establish connections Any containers running in the pod that need to establish connections
to dependencies must be reconfigured to use the local upstream address. to dependencies must be reconfigured to use the local upstream address.
This means pods should not use Kubernetes service DNS or environment This means pods should not use Kubernetes service DNS or environment
variables for these connections. variables for these connections.
We can verify access to the static text server using `kubectl exec`. Notice We can verify access to the static text server using `kubectl exec`. Notice
that we `curl` the local address and local port 1234 specified with our that we `curl` the local address and local port 1234 specified with our
upstreams. upstreams.