6 Commits (a884d0d7c71cb58a9e498100e1f7603632f86a33)

Author	SHA1	Message	Date
cskh	04bf24c8c1	feat(ingress-gateway): support outlier detection of upstream service for ingress gateway (#15614) ... * feat(ingress-gateway): support outlier detection of upstream service for ingress gateway * changelog Co-authored-by: Eric Haberkorn <erichaberkorn@gmail.com>	2022-12-13 11:51:37 -05:00
Paul Banks	81eb706906	Add Envoy integration test to show Header manip can interpolate Envoy variables	2021-09-10 21:09:24 +01:00
Paul Banks	1b9632531a	Integration tests for all new header manip features	2021-09-10 21:09:24 +01:00
Chris Piraino	1a853fc954	Always require Host header values for http services (#7990) ... Previously, we did not require the 'service-name.*' host header value when on a single http service was exposed. However, this allows a user to get into a situation where, if they add another service to the listener, suddenly the previous service's traffic might not be routed correctly. Thus, we always require the Host header, even if there is only 1 service. Also, we add the make the default domain matching more restrictive by matching "service-name.ingress.*" by default. This lines up better with the namespace case and more accurately matches the Consul DNS value we expect people to use in this case.	2020-06-08 13:16:24 -05:00
Chris Piraino	f40833d094	Allow Hosts field to be set on an ingress config entry ... - Validate that this cannot be set on a 'tcp' listener nor on a wildcard service. - Add Hosts field to api and test in consul config write CLI - xds: Configure envoy with user-provided hosts from ingress gateways	2020-05-06 15:06:13 -05:00
Kyle Havlovitz	e7b1ee55de	Add http routing support and integration test to ingress gateways	2020-04-24 09:31:32 -05:00