upstream: Fallback policy per selector support (#7087)
This code change allows to redefine fallback policy per specific subset selector. Because of how existing LbSubsetMap trie data structure is organised (mapping subset key to values), is not possible to do lookups for fallback policy only based on subset keys (had to introduce additional trie that maps subset keys to keys and has fallback policy on leaf level). Additional LbSubsetSelectorFallbackPolicy enum required to correctly identify the case when fallback policy is not set for given selector (otherwise it would always default to NO_FALLBACK, breaking backwards compatibility, if field is not set we should use top level fallback policy instead). Risk Level: Medium Testing: Done Docs Changes: Updated related docs Release Notes: added Fixes #5130 Signed-off-by: Kateryna Nezdolii <nezdolik@spotify.com> Mirrored from https://github.com/envoyproxy/envoy @ 1a60b343665cf2ffb966f37bbe48fed21805df57pull/620/head
parent
168fa5d1ae
commit
f7cfd4b8a4
1 changed files with 18 additions and 0 deletions
Loading…
Reference in new issue