-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Try MeshLoadBalancingStrategy
with MeshMultizoneService
#11968
Comments
Additionally, we need to ensure that when a user disables locality-aware routing using MeshLoadBalancingStrategy, traffic is properly distributed across zones. |
…ware is disabled (#11980) We already set `priority: 1` for remote zones in `fillRemoteMeshServices` so we need to explicitly set `priority: 0` if we _don't_ want locality awareness. Also fix an insufficient condition in an existing case, where we weren't verifying that requests really go to all zones, only that it's OK if they do. Fixes #11968 Signed-off-by: Mike Beaumont <[email protected]>
btw this is already the case |
Removing closed state labels due to the issue being reopened. |
We have two options to set locality-aware load balancing in Kuma:
These options allow control over whether traffic should be split across different zones or prioritized within the local zone.
When the locality-aware flag is enabled on the Mesh, traffic for kuma.io/service will remain within the same zone. The same effect occurs with MLBS: when set to true, traffic stays within the local zone. If both sets, MLBS can override it |
I think there is one more thing to try, we should check how we behave by the default (no policy/lb mesh configured) |
For this we have an e2e test I think right? It's locality aware |
Putting this back in pending so we discuss this |
|
Description
We should try
MeshLoadBalancingStrategy
withMeshMultizoneService
as it should behave differently that we should prioritize local zone instead of prioritizing splitting traffic between all zones.This is followup for: #11966
The text was updated successfully, but these errors were encountered: