consul/test
Freddy fdd10dd8b8
Expose HTTP-based paths through Connect proxy (#6446)
Fixes: #5396

This PR adds a proxy configuration stanza called expose. These flags register
listeners in Connect sidecar proxies to allow requests to specific HTTP paths from outside of the node. This allows services to protect themselves by only
listening on the loopback interface, while still accepting traffic from non
Connect-enabled services.

Under expose there is a boolean checks flag that would automatically expose all
registered HTTP and gRPC check paths.

This stanza also accepts a paths list to expose individual paths. The primary
use case for this functionality would be to expose paths for third parties like
Prometheus or the kubelet.

Listeners for requests to exposed paths are be configured dynamically at run
time. Any time a proxy, or check can be registered, a listener can also be
created.

In this initial implementation requests to these paths are not
authenticated/encrypted.
2019-09-25 20:55:52 -06:00
..
bin test: log exit code in cluster.bash 2017-06-08 14:06:10 +02:00
ca Update test certificates that expire this year to be way in the future 2018-05-12 10:15:45 +01:00
ca_path Add tls client options to api/cli 2017-04-14 13:37:29 -07:00
client_certs Adds enable_agent_tls_for_checks configuration option which allows (#3661) 2017-11-07 18:22:09 -08:00
command/merge Add utility types to enable checking for unset flags 2017-02-07 20:14:41 -05:00
hostname Update test certificates that expire this year to be way in the future 2018-05-12 10:15:45 +01:00
integration/connect/envoy Expose HTTP-based paths through Connect proxy (#6446) 2019-09-25 20:55:52 -06:00
key tls: auto_encrypt enables automatic RPC cert provisioning for consul clients (#5597) 2019-06-27 22:22:07 +02:00
snapshot snapshot: read meta.json correctly. (#5193) 2019-01-08 17:06:28 +01:00
notes.txt Adding testing certificates 2014-04-07 15:07:00 -07:00