consul/agent/proxycfg
freddygv ceb52d649a Account for upstream targets in another DC.
Transparent proxies typically cannot dial upstreams in remote
datacenters. However, if their upstream configures a redirect to a
remote DC then the upstream targets will be in another datacenter.

In that sort of case we should use the WAN address for the passthrough.
2022-02-10 17:01:57 -07:00
..
connect_proxy.go Fix race of upstreams with same passthrough ip 2022-02-10 17:01:57 -07:00
ingress_gateway.go proxycfg: introduce explicit UpstreamID in lieu of bare string (#12125) 2022-01-20 10:12:04 -06:00
manager.go reset `coalesceTimer` to nil as soon as the event is consumed (#11924) 2022-01-05 12:17:47 -05:00
manager_test.go Fix race of upstreams with same passthrough ip 2022-02-10 17:01:57 -07:00
mesh_gateway.go Store GatewayKey in proxycfg snapshot for re-use 2021-11-01 13:58:53 -06:00
mesh_gateway_oss.go re-run gofmt on 1.17 (#11579) 2021-11-16 12:04:01 -06:00
naming.go Ensure passthrough addresses get cleaned up 2022-02-10 17:01:57 -07:00
naming_oss.go proxycfg: introduce explicit UpstreamID in lieu of bare string (#12125) 2022-01-20 10:12:04 -06:00
naming_test.go Ensure passthrough addresses get cleaned up 2022-02-10 17:01:57 -07:00
proxycfg.go
snapshot.go Fix race of upstreams with same passthrough ip 2022-02-10 17:01:57 -07:00
state.go Fix race of upstreams with same passthrough ip 2022-02-10 17:01:57 -07:00
state_test.go Account for upstream targets in another DC. 2022-02-10 17:01:57 -07:00
terminating_gateway.go Store GatewayKey in proxycfg snapshot for re-use 2021-11-01 13:58:53 -06:00
testing.go proxycfg: introduce explicit UpstreamID in lieu of bare string (#12125) 2022-01-20 10:12:04 -06:00
upstreams.go Account for upstream targets in another DC. 2022-02-10 17:01:57 -07:00