route_configuration
defined in SRDS is not being picked up
#33519
Labels
route_configuration
defined in SRDS is not being picked up
#33519
If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
envoy-security@googlegroups.com where the issue will be triaged appropriately.
Title: The
route_configuration
field in the type,[envoy.config.route.v3.ScopedRouteConfiguration](https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/scoped_route.proto#envoy-v3-api-msg-config-route-v3-scopedrouteconfiguration)
is not utilized when it is used via SRDSDescription:
I have Scoped Routes defined in a
ScopedRouteConfiguration
withroute_configuration
defined inline instead of throughroute_configuration_name
. It looks like some config validator is blocking consumption of this field whenever it's read in via SRDS:Error:
If I specify a
route_configuration_name
under the srds.yaml config, I get the following error:Repro steps:
I'm utilizing the filesystem xDS mechanisms for setting up Envoy.
srds.yaml (For Scoped Route Discovery Service)
lds.yaml (For Listener Discovery Service)
static envoy config:
Admin and Stats Output:
Config:
Logs:
Call Stack:
The text was updated successfully, but these errors were encountered: