consul/ingress-with-chain.golden at f40833d094f8d2f389cd4a292ba5bb784833fd09 - consul - Status.im Repos

status-im/consul

mirror of https://github.com/status-im/consul.git synced 2025-01-10 05:45:46 +00:00

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

7 lines

144 B

Plaintext

Raw Blame History

 {
   "versionInfo": "00000001",
   "resources": [
   ],
   "typeUrl": "type.googleapis.com/envoy.api.v2.RouteConfiguration",
   "nonce": "00000001"
 }