consul/agent/xds/testdata/endpoints
Freddy 9ed325ba8b
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 15:28:45 -06:00
..
connect-proxy-with-chain-and-failover.golden
connect-proxy-with-chain-and-overrides.golden
connect-proxy-with-chain-external-sni.golden
connect-proxy-with-chain.golden
connect-proxy-with-default-chain-and-custom-cluster.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 15:28:45 -06:00
connect-proxy-with-tcp-chain-double-failover-through-local-gateway-triggered.golden
connect-proxy-with-tcp-chain-double-failover-through-local-gateway.golden
connect-proxy-with-tcp-chain-double-failover-through-remote-gateway-triggered.golden
connect-proxy-with-tcp-chain-double-failover-through-remote-gateway.golden
connect-proxy-with-tcp-chain-failover-through-local-gateway-triggered.golden
connect-proxy-with-tcp-chain-failover-through-local-gateway.golden
connect-proxy-with-tcp-chain-failover-through-remote-gateway-triggered.golden
connect-proxy-with-tcp-chain-failover-through-remote-gateway.golden
defaults.golden
ingress-gateway-no-services.golden
ingress-gateway.golden
ingress-multiple-listeners-duplicate-service.golden Support multiple listeners referencing the same service in gateway definitions 2020-05-06 15:06:13 -05:00
ingress-splitter-with-resolver-redirect.golden
ingress-with-chain-and-failover.golden
ingress-with-chain-and-overrides.golden
ingress-with-chain-external-sni.golden
ingress-with-chain.golden
ingress-with-tcp-chain-double-failover-through-local-gateway-triggered.golden Allow ingress gateways to route through mesh gateways 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-double-failover-through-local-gateway.golden
ingress-with-tcp-chain-double-failover-through-remote-gateway-triggered.golden Allow ingress gateways to route through mesh gateways 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-double-failover-through-remote-gateway.golden
ingress-with-tcp-chain-failover-through-local-gateway-triggered.golden Allow ingress gateways to route through mesh gateways 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-failover-through-local-gateway.golden
ingress-with-tcp-chain-failover-through-remote-gateway-triggered.golden Allow ingress gateways to route through mesh gateways 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-failover-through-remote-gateway.golden
mesh-gateway-default-service-subset.golden
mesh-gateway-no-services.golden
mesh-gateway-service-subsets.golden
mesh-gateway-using-federation-states.golden
mesh-gateway.golden
splitter-with-resolver-redirect.golden
terminating-gateway-default-service-subset.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 15:28:45 -06:00
terminating-gateway-no-services.golden Add xds cluster/listener/endpoint management 2020-04-27 11:08:40 -06:00
terminating-gateway-service-subsets.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 15:28:45 -06:00
terminating-gateway.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 15:28:45 -06:00