caa5b5a5a6
Fixes an issue described in #10132, where if two DCs are WAN federated over mesh gateways, and the gateway in the non-primary DC is terminated and receives a new IP address (as is commonly the case when running them on ephemeral compute instances) the primary DC is unable to re-establish its connection until the agent running on its own gateway is restarted. This was happening because we always preferred gateways discovered by the `Internal.ServiceDump` RPC (which would fail because there's no way to dial the remote DC) over those discovered in the federation state, which is replicated as long as the primary DC's gateway is reachable. |
||
|---|---|---|
| .. | ||
| connect_proxy.go | ||
| ingress_gateway.go | ||
| manager.go | ||
| manager_test.go | ||
| mesh_gateway.go | ||
| mesh_gateway_oss.go | ||
| proxycfg.go | ||
| snapshot.go | ||
| state.go | ||
| state_test.go | ||
| terminating_gateway.go | ||
| testing.go | ||
| upstreams.go | ||