mirror of https://github.com/hashicorp/consul
dfab5ade50
When a large number of upstreams are configured on a single envoy proxy, there was a chance that it would timeout when waiting for ClusterLoadAssignments. While this doesn't always immediately cause issues, consul-dataplane instances appear to consistently drop endpoints from their configurations after an xDS connection is re-established (the server dies, random disconnect, etc). This commit adds an `xds_fetch_timeout_ms` config to service registrations so that users can set the value higher for large instances that have many upstreams. The timeout can be disabled by setting a value of `0`. This configuration was introduced to reduce the risk of causing a breaking change for users if there is ever a scenario where endpoints would never be received. Rather than just always blocking indefinitely or for a significantly longer period of time, this config will affect only the service instance associated with it. |
||
---|---|---|
.. | ||
internal/watch | ||
api_gateway.go | ||
api_gateway_ce.go | ||
config_snapshot_glue.go | ||
config_snapshot_glue_test.go | ||
connect_proxy.go | ||
data_sources.go | ||
data_sources_ce.go | ||
deep-copy.sh | ||
ingress_gateway.go | ||
manager.go | ||
manager_test.go | ||
mesh_gateway.go | ||
mesh_gateway_ce.go | ||
naming.go | ||
naming_ce.go | ||
naming_test.go | ||
proxycfg.deepcopy.go | ||
proxycfg.go | ||
snapshot.go | ||
snapshot_test.go | ||
state.go | ||
state_ce_test.go | ||
state_test.go | ||
terminating_gateway.go | ||
testing.go | ||
testing_api_gateway.go | ||
testing_ce.go | ||
testing_connect_proxy.go | ||
testing_ingress_gateway.go | ||
testing_mesh_gateway.go | ||
testing_peering.go | ||
testing_terminating_gateway.go | ||
testing_tproxy.go | ||
testing_upstreams.go | ||
testing_upstreams_ce.go | ||
upstreams.go |