envoyproxy / envoyproxy/envoy

eds: envoy is sending EDS discovery request without any resource_names set

Open
#7,529 59 comments 0 reactions 1 assignee Claimed by @dmitri-d View on GitHub
bug help wanted
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
428

Description

*Title*: Envoy is sending EDS discovery request without any resource_names set

*Description*:
Lyft has noticed envoy requesting EDS data without resouce_names set. It is sporadic throughout all services. This is happening enough where our control plane started to page (as our control plane treats this request as an error).

We noticed that the envoy discovery request payload always has a version set and a response_nonce set. So Envoy does have historical EDS data, thus didn't notice any degradation in the data plane.

*Logs*:
Here is a sample request payload coming from our control plane logs.

```json
{
"version_info": "6682668b14343e6a63e29e538a9839dfb46c647d",
"node": {
"id": "06699ec750c498729",
"cluster": "roadspinned-production-iad",
"locality": {
"zone": "us-east-1f"
},
"build_version": "7e8f440546bd920c2468b0e379798a79547ca2ca/1.11.0-dev/Modified/RELEASE/BoringSSL"
},
"type_url": "type.googleapis.com/envoy.api.v2.ClusterLoadAssignment",
"response_nonce": "36"
}
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.