luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-consul/test/integration/connect/envoy/case-ingress-gateway-multip...
History
Kyle Havlovitz b21cd112e5 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
..
capture.sh Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00
config_entries.hcl Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00
gateway.hcl Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00
setup.sh Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00
vars.sh Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00
verify.bats Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00