d57f04fd5b
When consul is restarted and an envoy that had already sent DiscoveryRequests to the previous consul process sends a request to the new process it doesn't respect the setting and never populates DiscoveryRequest.Node for the life of the new consul process due to this bug: https://github.com/envoyproxy/envoy/issues/9682 Fixes #8430 |
||
---|---|---|
.. | ||
ca | ||
envoy | ||
expose | ||
proxy | ||
connect.go | ||
connect_test.go |