open-consul/test/integration/connect/envoy/case-ingress-gateway-multip.../setup.sh

#!/bin/bash

set -euo pipefail

# wait for bootstrap to apply config entries
wait_for_config_entry ingress-gateway ingress-gateway
wait_for_config_entry proxy-defaults global

gen_envoy_bootstrap ingress-gateway 20000 primary true
gen_envoy_bootstrap s1 19000
gen_envoy_bootstrap s2 19001
Allow ingress gateways to route traffic based on Host header This commit adds the necessary changes to allow an ingress gateway to route traffic from a single defined port to multiple different upstream services in the Consul mesh. To do this, we now require all HTTP requests coming into the ingress gateway to specify a Host header that matches "<service-name>.*" in order to correctly route traffic to the correct service. - Differentiate multiple listener's route names by port - Adds a case in xds for allowing default discovery chains to create a route configuration when on an ingress gateway. This allows default services to easily use host header routing - ingress-gateways have a single route config for each listener that utilizes domain matching to route to different services. 2020-04-16 23:24:11 +00:00			`#!/bin/bash`

			`set -euo pipefail`

			`# wait for bootstrap to apply config entries`
			`wait_for_config_entry ingress-gateway ingress-gateway`
			`wait_for_config_entry proxy-defaults global`

			`gen_envoy_bootstrap ingress-gateway 20000 primary true`
			`gen_envoy_bootstrap s1 19000`
			`gen_envoy_bootstrap s2 19001`