Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
resolver: State: add Endpoints and deprecate Addresses #6471
resolver: State: add Endpoints and deprecate Addresses #6471
Changes from all commits
1ef2bfd
ef79b22
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Is this supposed to be only for the
xds
scheme or do we plan to add this for thexdstp
scheme as well?Also, could you help me figure out how this is used. The code in
stream.go
adds the metadata, but I don't see how or where this is used. Thanks.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.
Are we supporting
xdstp
for the target string? If so, this needs to be extended.This is read here when doing metadata matching for routes:
grpc-go/xds/internal/xdsclient/xdsresource/matcher.go
Line 100 in 2aa2615
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.
Hmm ... A47 section on target-uri syntax says we will continue to support the
xds
scheme for convenience. It does not say that we will start supporting thexdstp
scheme. Nor does it say we will not support thexdstp
scheme and instead the translations will be handled by the bootstrap configuration.Do you think we should improve the language in this gRFC section or is it clear to you?
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.
It's not super air-tight, but by not saying "we're supporting
xdstp
as a gRPC name resolver scheme and here's how", then I wouldn't assume we are adding it. We'd need a spec for how to handle it as a channel-level target. The text that follows does describe how we'll support this new stuff in the existingxds
resolver instead of adding a top-level resolver scheme forxdstp
: