status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
consul/agent/xds/testdata/clusters
History
Freddy 5d2475232a 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 18:51:33 -06:00
..
connect-proxy-with-chain-and-failover.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-chain-and-overrides.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-chain-external-sni.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-chain.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-tcp-chain-double-failover-through-local-gateway-triggered.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-tcp-chain-double-failover-through-local-gateway.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-tcp-chain-double-failover-through-remote-gateway-triggered.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-tcp-chain-double-failover-through-remote-gateway.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-tcp-chain-failover-through-local-gateway-triggered.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-tcp-chain-failover-through-local-gateway.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-tcp-chain-failover-through-remote-gateway-triggered.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
connect-proxy-with-tcp-chain-failover-through-remote-gateway.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
custom-limits-max-connections-only.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
custom-limits-set-to-zero.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
custom-limits.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
custom-local-app.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
custom-timeouts.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
custom-upstream-default-chain.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
custom-upstream.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
defaults.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
expose-paths-grpc-new-cluster-http1.golden proxycfg: support path exposed with non-HTTP2 protocol (#7510) 2020-04-02 09:35:04 +02:00
expose-paths-local-app-paths.golden Expose HTTP-based paths through Connect proxy (#6446) 2019-09-25 20:55:52 -06:00
expose-paths-new-cluster-http2.golden Expose HTTP-based paths through Connect proxy (#6446) 2019-09-25 20:55:52 -06:00
ingress-gateway-no-services.golden Ingress Gateways for TCP services (#7509) 2020-04-16 14:00:48 -07:00
ingress-gateway.golden Ingress Gateways for TCP services (#7509) 2020-04-16 14:00:48 -07:00
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 Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-chain-and-failover.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-chain-and-overrides.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-chain-external-sni.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-chain.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-double-failover-through-local-gateway-triggered.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-double-failover-through-local-gateway.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-double-failover-through-remote-gateway-triggered.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-double-failover-through-remote-gateway.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-failover-through-local-gateway-triggered.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-failover-through-local-gateway.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-failover-through-remote-gateway-triggered.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
ingress-with-tcp-chain-failover-through-remote-gateway.golden Add all the xds ingress tests 2020-04-24 09:31:32 -05:00
mesh-gateway-ignore-extra-resolvers.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 18:51:33 -06:00
mesh-gateway-no-services.golden agent: allow mesh gateways to initialize even if there are no connect services registered yet (#6576) 2019-10-17 16:46:49 -05:00
mesh-gateway-service-subsets.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 18:51:33 -06:00
mesh-gateway-service-timeouts.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 18:51:33 -06:00
mesh-gateway-using-federation-states.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 18:51:33 -06:00
mesh-gateway.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 18:51:33 -06:00
splitter-with-resolver-redirect.golden Allow configuration of upstream connection limits in Envoy (#6829) 2019-12-03 14:13:33 -06:00
terminating-gateway-hostname-service-subsets.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 18:51:33 -06:00
terminating-gateway-ignore-extra-resolvers.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 18:51:33 -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 18:51:33 -06:00
terminating-gateway.golden Enable gateways to resolve hostnames to IPv4 addresses (#7999) 2020-06-03 18:51:33 -06:00