Open zp9763 opened 2 months ago
Currently this is not supported by Envoy - it will reject response resources with ResourceName.
FWIW, at the moment Envoy will not reject the response but just disregards the field, as it only looks for the name field. It is also worth noting that I'm not aware of any xDS client that supports this field for now (see gRPC support for the name
field). That said, eventually this should be supported by Envoy.
cc @krajshiva as this request is from an internal Google team, and we can add it as part of the xDS-TP/Federation work.
Hey, this looks interesting. Is this something I can be assigned?
Hey, this looks interesting. Is this something I can be assigned?
@RaviTriv sure, thanks!
Awesome. Getting started on this.
Looks like this is the same as https://github.com/envoyproxy/envoy/issues/14428. I'm not actively working on it, but just wanted to link the two issues.
@RaviTriv are you currently working on this issue?
Hey @tonya11en. I haven't made much progress on this issue yet but I would like to continue on this issue if its not something that needs to be done urgently. Thank you!
No worries, we don't need this right away. If that changes I'll check back in before we start any work.
Title: Support
envoy.service.discovery.v3.ResourceName
in response resources.Description: envoy.service.discovery.v3.Resource definition has either
name
orresource_name
field to distinguish it from other resources of the same type. envoy.service.discovery.v3.ResourceName is designed to allow multiple variants of the named resource that are differentiated by dynamic parameter constraints. Currently this is not supported by Envoy - it will reject response resources with ResourceName.