ringhash: make endpoint hash key configurable, and set it from EDS #7161
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implement part 2 of A76: the ability to specify the location of endpoints on the ring, and a default implementation based on EDS metadata that matches Envoy behavior.
atollena
force-pushed
the
A76-hash-key-endpoint-attribute
branch
from
2fe5b52 to
e1bf6bf
Compare
|
Ready to review, will wait for A76 to be merged before merging this. |
|
Closing until the rest of the work in this gRFC is properly implemented. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Implement part 2 of A76: the ability to specify the location of endpoints on the ring, and a default implementation based on EDS metadata that matches Envoy behavior.
RELEASE NOTES: