consul/test/integration/connect/envoy/case-http2
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
..
capture.sh Expose HTTP-based paths through Connect proxy (#6446) 2019-09-25 20:55:52 -06:00
s1.hcl Connect: allow configuring Envoy for L7 Observability (#5558) 2019-04-29 17:27:57 +01:00
s2.hcl Connect: allow configuring Envoy for L7 Observability (#5558) 2019-04-29 17:27:57 +01:00
setup.sh Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
verify.bats xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00