-
Notifications
You must be signed in to change notification settings - Fork 3.9k
xds: integrate usage of XdsClient in XdsNameResolver #6504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xds: integrate usage of XdsClient in XdsNameResolver #6504
Conversation
b7e4ce6 to
4e933a1
Compare
4e933a1 to
2596d97
Compare
2596d97 to
8594106
Compare
ef6af6e to
10eec0c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@ericgribkoff Can you please run a staging test to see if it works before merging? With this PR the full XdsNameResolver -> LDS -> RDS -> CDS -> EDS flow will run. Previously only XdsNameresolver -> EDS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to merge.
Incorporating comment #6504 (comment). Currently there is no cross-language resolver sending CDS config so there is no impact of the change.
When
XdsNameResolverstarts, it instantiate anXdsClientinstance to send out an xDS discovery RPC resolving cluster name for gRPC target. When a result found, return aResolutionResultwith service config containingcds_experimentalas the load balancing config to the channel. The instantiatedXdsClientinstance is also passed as anResolutionResult.Attributesto channel.