consul/agent/proxycfg
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
..
manager.go Add proxycfg state management for terminating-gateways 2020-04-27 11:07:06 -06:00
manager_test.go Ingress Gateways for TCP services (#7509) 2020-04-16 14:00:48 -07:00
proxycfg.go Proxy Config Manager (#4729) 2018-10-10 16:55:34 +01:00
snapshot.go Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00
state.go Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00
state_test.go Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00
testing.go Allow ingress gateways to route traffic based on Host header 2020-05-06 15:06:13 -05:00