consul

History

R.B. Boyer 20caa4f744 test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 ) When the envoy healthy panic threshold was explicitly disabled as part of L7 traffic management it changed how envoy decided to load balance to endpoints in a cluster. This only matters when envoy is in "panic mode" aka "when you have a bunch of unhealthy endpoints". Panic mode sends traffic to unhealthy instances in certain circumstances. Note: Prior to explicitly disabling the healthy panic threshold, the default value is 50%. What was happening is that the test harness was bringing up consul the sidecars, and the service instances all at once and sometimes the proxies wouldn't have time to be checked by consul to be labeled as 'passing' in the catalog before a round of EDS happened. The xDS server in consul effectively queries /v1/health/connect/s2 and gets 1 result, but that one result has a 'critical' check so the xDS server sends back that endpoint labeled as UNHEALTHY. Envoy sees that 100% of the endpoints in the cluster are unhealthy and would enter panic mode and still send traffic to s2. This is why the test suites PRIOR to disabling the healthy panic threshold worked. They were _incorrectly_ passing. When the healthy panic threshol is disabled, envoy never enters panic mode in this situation and thus the cluster has zero healthy endpoints so load balancing goes nowhere and the tests fail. Why does this only affect the test suites for envoy 1.8.0? My guess is that https://github.com/envoyproxy/envoy/pull/4442 was merged into the 1.9.x series and somehow that plays a role. This PR modifies the bats scripts to explicitly wait until the upstream sidecar is healthy as measured by /v1/health/connect/s2?passing BEFORE trying to interrogate envoy which should make the tests less racy.		5 years ago
..
case-badauthz	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
case-basic	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
case-centralconf	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
case-consul-exec	…
case-dogstatsd-udp	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
case-grpc	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
case-http	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
case-http-badauthz	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
case-http2	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
case-prometheus	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
case-statsd-udp	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
case-zipkin	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
consul-base-cfg	…
.gitignore	…
Dockerfile-bats	…
Dockerfile-consul-envoy	…
docker-compose.yml	…
helpers.bash	test: for envoy integration tests, wait until 's2' is healthy in consul before interrogating envoy (#6108 )	5 years ago
run-tests.sh	…