command/connect/proxy: detailed help

This commit is contained in:
Mitchell Hashimoto 2018-05-19 11:34:00 -07:00
parent 01c3564158
commit 82ba167757
No known key found for this signature in database
GPG Key ID: 744E147AA52F5B0A
1 changed files with 28 additions and 1 deletions

View File

@ -254,7 +254,34 @@ func (c *cmd) Help() string {
const synopsis = "Runs a Consul Connect proxy" const synopsis = "Runs a Consul Connect proxy"
const help = ` const help = `
Usage: consul proxy [options] Usage: consul connect proxy [options]
Starts a Consul Connect proxy and runs until an interrupt is received. Starts a Consul Connect proxy and runs until an interrupt is received.
The proxy can be used to accept inbound connections for a service,
wrap outbound connections to upstream services, or both. This enables
a non-Connect-aware application to use Connect.
The proxy requires service:write permissions for the service it represents.
Consul can automatically start and manage this proxy by specifying the
"proxy" configuration within your service definition.
The example below shows how to start a local proxy for establishing outbound
connections to "db" representing the frontend service. Once running, any
process that creates a TCP connection to the specified port (8181) will
establish a mutual TLS connection to "db" identified as "frontend".
$ consul connect proxy -service frontend -upstream db:8181
The next example starts a local proxy that also accepts inbound connections
on port 8443, authorizes the connection, then proxies it to port 8080:
$ consul connect proxy \
-service frontend \
-service-addr 127.0.0.1:8080 \
-listen ':8443'
A proxy can accept both inbound connections as well as proxy to upstream
services by specifying both the "-listen" and "-upstream" flags.
` `