You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title: Provide a way to attach dynamic data to Host object
Description:
I'm prototyping a new LB policy that will calculate host weights for WRR locally, based on custom headers attached to the backend responses.
Are you trying to do something where the upstream hosts report their load via response headers and scale weights based on this? If so, it's the same as the ongoing conversation in #20907.
Otherwise, if you're implementing a custom LB extension are you not able to modify the Host objects in the implementation or keep some mapping of host->derived weight?
Are you suggesting to extend Host object specifically in custom LB extension or something else?
Keeping some mapping of host->derived is certainly an option, but seems a bit clunky.
Title: Provide a way to attach dynamic data to Host object
Description:
I'm prototyping a new LB policy that will calculate host weights for WRR locally, based on custom headers attached to the backend responses.
The LB policy needs to keep dynamic internal data on per host basis, similar to HostDescription::metadata()
I think FilterState serves similar purpose, but it doesn't attach to a Host.
Are there better alternatives, or would it be possible to attach dynamic data (similar to FilterState) to a
Host
orHostDescription
?The text was updated successfully, but these errors were encountered: