Send user defined metadata to the client#1112
Merged
agrawroh merged 1 commit intoenvoyproxy:mainfrom Apr 19, 2026
Merged
Conversation
Signed-off-by: Yan Avlasov <yavlasov@google.com>
agrawroh
approved these changes
Apr 19, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add per descriptor metadata that is sent to the client when the descriptor is under the limit.
This is a prerequisite for the quota based routing. The rate limit service will send metadata with the service names that correspond to descriptors with available quota. Envoy will use this metadata to select a service for forwarding the request.