consul/test
Kyle Havlovitz 247f9eaf13 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-05-06 15:06:13 -05:00
..
bin test: log exit code in cluster.bash 2017-06-08 14:06:10 +02:00
ca Update test certificates that expire this year to be way in the future 2018-05-12 10:15:45 +01:00
ca_path Add tls client options to api/cli 2017-04-14 13:37:29 -07:00
client_certs Adds enable_agent_tls_for_checks configuration option which allows (#3661) 2017-11-07 18:22:09 -08:00
command/merge Add utility types to enable checking for unset flags 2017-02-07 20:14:41 -05:00
hostname wan federation via mesh gateways (#6884) 2020-03-09 15:59:02 -05:00
integration/connect/envoy Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00
key tls: auto_encrypt enables automatic RPC cert provisioning for consul clients (#5597) 2019-06-27 22:22:07 +02:00
snapshot snapshot: read meta.json correctly. (#5193) 2019-01-08 17:06:28 +01:00
notes.txt Adding testing certificates 2014-04-07 15:07:00 -07:00