Location based Load Balancing (cherry-pick #10720 from release-1.1 to master)#11256
Merged
istio-testing merged 2 commits intoistio:masterfrom Jan 25, 2019
Merged
Location based Load Balancing (cherry-pick #10720 from release-1.1 to master)#11256istio-testing merged 2 commits intoistio:masterfrom
istio-testing merged 2 commits intoistio:masterfrom
Conversation
Implement locality aware routing based on Envoy lbEndpoints priority. Traffic will be routed to endpoints in same subzone, then failover to all in same zone, then failover to all in same region. This is the typical expected behavior for most setups. The explicit failover to a specific region allows people to maintain traffic within the same country if desired. Support Locality weighted load balancing. In order to use this feature, DestinationRule.TrafficPolicy.LoadBalancer.LocalityWeightSettings has to be configured. Currently we support specifying each groups of locality endpoints with a weight. For example , traffic locality A --> locality A with 80% locality A --> locality B with 10% locality A --> locality C with 10%
Collaborator
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hzxuzhonghu, rshriram The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Collaborator
|
@hzxuzhonghu: The following test failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Support Locality-weighted load balancing
Allows administrators to control the distribution of traffic to endpoints based on the localities of where the traffic originates and where it will terminate. These localities are specified using arbitrary labels that designate a hierarchy of localities in {region}/{zone}/{sub-zone} form. For additional detail refer to https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/load_balancing/locality_weight
Implement locality aware routing based on Envoy lbEndpoints priority.
By default traffic will be routed to endpoints in same {region}/{zone}/{sub-zone}, then failover to all in same {region}/{zone}, then failover to all in same {region}, at last failover to those in other regions. This is the typical expected behavior for most setups. The explicit Failover setting to a specific region allows admins to restrict the regionality of failover. Assume a service resides in zones within us-east, us-west & eu-west, when endpoints within us-east become unhealthy traffic should failover to endpoints within eu-west and similarly us-west should failover to us-east.