consul/test/integration/connect/envoy
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
..
case-badauthz Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
case-basic Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
case-centralconf Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
case-cfg-resolver-dc-failover-gateways-none tests: make envoy integration tests more tolerant of internal retries that may inflate counters (#6539) 2019-09-25 09:08:42 -05:00
case-cfg-resolver-dc-failover-gateways-remote tests: make envoy integration tests more tolerant of internal retries that may inflate counters (#6539) 2019-09-25 09:08:42 -05:00
case-cfg-resolver-defaultsubset Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
case-cfg-resolver-subset-onlypassing Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
case-cfg-resolver-subset-redirect Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
case-cfg-resolver-svc-failover Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
case-cfg-resolver-svc-redirect Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
case-consul-exec Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
case-dogstatsd-udp xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
case-gateways-local tests: make envoy integration tests more tolerant of internal retries that may inflate counters (#6539) 2019-09-25 09:08:42 -05:00
case-gateways-remote tests: make envoy integration tests more tolerant of internal retries that may inflate counters (#6539) 2019-09-25 09:08:42 -05:00
case-grpc xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
case-http xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
case-http-badauthz xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
case-http2 Expose HTTP-based paths through Connect proxy (#6446) 2019-09-25 20:55:52 -06:00
case-prometheus xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
case-statsd-udp xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
case-zipkin xds: improve how envoy metrics are emitted (#6312) 2019-08-16 09:30:17 -05:00
consul-base-cfg Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
.gitignore activate most discovery chain features in xDS for envoy (#6024) 2019-07-01 22:10:51 -05:00
Dockerfile-bats
Dockerfile-consul-envoy
defaults.sh Envoy Mesh Gateway integration tests (#6187) 2019-07-24 17:01:42 -04:00
docker-compose.yml connect: fix failover through a mesh gateway to a remote datacenter (#6259) 2019-08-05 13:30:35 -05:00
helpers.bash tests: make envoy integration tests more tolerant of internal retries that may inflate counters (#6539) 2019-09-25 09:08:42 -05:00
run-tests.sh [BUGFIX][BUILD] When test fail in circle-ci in main, have a proper error message (#6416) 2019-08-28 10:26:05 -04:00