Takeshi Yoneda
Takeshi Yoneda
yeah i guess at least users can define whatever dummy service in anyway if that doesn't work them. so +1 to go with focusing on BTP enhancement
i would prefer option 2.
> the HostOverride lbPolicy requires the fallback upstream is this true at Envoy level? If so, maybe we can just insert some random backend. If this is at the EG...
Let me clarify that we have two "fallbacks" we are talking about. One fallback is the envoy cluster configuration level endpoint that must exist (as you found that without which...
i won't be able to have cycles to land this - closing 🙏
cc @marc-barry ps the flaky CI failure is nothing to do with this PR > ERROR: /source/test/extensions/load_balancing_policies/client_side_weighted_round_robin/BUILD:40:24: Compiling test/extensions/load_balancing_policies/client_side_weighted_round_robin/integration_test.cc failed: (Killed): clang-14 failed: error executing command (from target //test/extensions/load_balancing_policies/client_side_weighted_round_robin:integration_test)
no idea why suddenly gcc is getting killed ... (merged main again and hope all good)
~hmm looks legit and~ failed to reproduce locally either.. found the exact same failure on main: https://github.com/envoyproxy/envoy/actions/runs/11463146676/job/31896388874