open-consul/test/integration/connect/envoy/case-terminating-gateway-ho.../setup.sh

#!/bin/bash

set -euo pipefail

# wait for bootstrap to apply config entries
wait_for_config_entry terminating-gateway terminating-gateway

register_services primary

gen_envoy_bootstrap terminating-gateway 20000 primary true
gen_envoy_bootstrap s1 19000
Enable gateways to resolve hostnames to IPv4 addresses (#7999) The DNS resolution will be handled by Envoy and defaults to LOGICAL_DNS. This discovery type can be overridden on a per-gateway basis with the envoy_dns_discovery_type Gateway Option. If a service contains an instance with a hostname as an address we set the Envoy cluster to use DNS as the discovery type rather than EDS. Since both mesh gateways and terminating gateways route to clusters using SNI, whenever there is a mix of hostnames and IP addresses associated with a service we use the hostname + CDS rather than the IPs + EDS. Note that we detect hostnames by attempting to parse the service instance's address as an IP. If it is not a valid IP we assume it is a hostname. 2020-06-03 21:28:45 +00:00			`#!/bin/bash`

			`set -euo pipefail`

			`# wait for bootstrap to apply config entries`
			`wait_for_config_entry terminating-gateway terminating-gateway`

test: use direct service registration in envoy integration tests (#9138) This has the biggest impact on enterprise test cases that use namespaced registrations, which prior to this change sometimes failed the initial registration because the namespace was not yet created. 2020-11-09 19:59:46 +00:00			`register_services primary`

Enable gateways to resolve hostnames to IPv4 addresses (#7999) The DNS resolution will be handled by Envoy and defaults to LOGICAL_DNS. This discovery type can be overridden on a per-gateway basis with the envoy_dns_discovery_type Gateway Option. If a service contains an instance with a hostname as an address we set the Envoy cluster to use DNS as the discovery type rather than EDS. Since both mesh gateways and terminating gateways route to clusters using SNI, whenever there is a mix of hostnames and IP addresses associated with a service we use the hostname + CDS rather than the IPs + EDS. Note that we detect hostnames by attempting to parse the service instance's address as an IP. If it is not a valid IP we assume it is a hostname. 2020-06-03 21:28:45 +00:00			`gen_envoy_bootstrap terminating-gateway 20000 primary true`
			`gen_envoy_bootstrap s1 19000`