xds: sync envoy proto to commit 62ca8bd2b5960ed1c6ce2be97d3120cee719ecab #8346
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
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.
Sync to the latest update to pick up envoyproxy/envoy#16942 for forward compatibility with upcoming xDS Rate Limiting features.
Internal Envoy import CL for
62ca8bd2b5960ed1c6ce2be97d3120cee719ecab: cl/381356375Suppressed warnings for newly deprecated xDS proto fields
PerXdsConfig xds_configto be replaced withGenericXdsConfig generic_xds_configs, but this work yet to be planned by @lidizhengHttpConnectionManager'suint32 setXffNumTrustedHopsto be replaced withTypedExtensionConfig OriginalIpDetectionExtensions. I don't know if there's any significance in testing that this exact field isn't supported. I can add a test forOriginalIpDetectionExtensionstoo.