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
We'd like to be able to weight address pools by node, so if a service is bound to an endpoint on a specific node, that node's address pool is preferred as a priority.
The reason for this is with a globally distributed cluster and address pools for each region, to enable the lowest latency service we should be able to dynamically issue IP addresses closest to the origin.
Thanks
The text was updated successfully, but these errors were encountered:
ChipWolf
changed the title
Annotate nodes with address pool
Annotate nodes with address pool/weighted address pools
Sep 7, 2021
Hi @ChipWolf , adding a node selector to the AddressPool object is currently part of this proposal
Would that solve your issue? As part of that, the idea is to enable the TrafficPolicy local for L2 load balancing. With that, metallb will advertise from a node selected by the selector AND with a running backend pod.
We'd like to be able to weight address pools by node, so if a service is bound to an endpoint on a specific node, that node's address pool is preferred as a priority.
The reason for this is with a globally distributed cluster and address pools for each region, to enable the lowest latency service we should be able to dynamically issue IP addresses closest to the origin.
Thanks
The text was updated successfully, but these errors were encountered: