open-consul/test/integration/connect/envoy/case-ingress-gateway-multiple-services/gateway.hcl at 3c2b23cccbff4f01450372f5716e0ea59f46cf2d - luxolus/open-consul - Stateless Git Forge

luxolus/open-consul

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

5 lines

67 B

HCL

Raw Blame History

 services {
   name = "ingress-gateway"
   kind = "ingress-gateway"
 }