程序包 istio.networking.v1alpha3

类 DestinationRuleOuterClass.LocalityLoadBalancerSetting.Builder

  • 所有已实现的接口:
    com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, DestinationRuleOuterClass.LocalityLoadBalancerSettingOrBuilder, java.lang.Cloneable
    封闭类:
    DestinationRuleOuterClass.LocalityLoadBalancerSetting
    public static final class DestinationRuleOuterClass.LocalityLoadBalancerSetting.Builder
extends com.google.protobuf.GeneratedMessageV3.Builder<DestinationRuleOuterClass.LocalityLoadBalancerSetting.Builder>
implements DestinationRuleOuterClass.LocalityLoadBalancerSettingOrBuilder
     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
 [Locality Weight](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/locality_weight)
 The following example shows how to setup locality weights mesh-wide.
 Given a mesh with workloads and their service deployed to "us-west/zone1/*"
 and "us-west/zone2/*". This example specifies that when traffic accessing a
 service originates from workloads in "us-west/zone1/*", 80% of the traffic
 will be sent to endpoints in "us-west/zone1/*", i.e the same zone, and the
 remaining 20% will go to endpoints in "us-west/zone2/*". This setup is
 intended to favor routing traffic to endpoints in the same locality.
 A similar setting is specified for traffic originating in "us-west/zone2/*".
 ```yaml
   distribute:
     - from: us-west/zone1/*
       to:
         "us-west/zone1/*": 80
         "us-west/zone2/*": 20
     - from: us-west/zone2/*
       to:
         "us-west/zone1/*": 20
         "us-west/zone2/*": 80
 ```
 If the goal of the operator is not to distribute load across zones and
 regions but rather to restrict the regionality of failover to meet other
 operational requirements an operator can set a 'failover' policy instead of
 a 'distribute' policy.
 The following example sets up a locality failover policy for regions.
 Assume a service resides in zones within us-east, us-west & eu-west
 this example specifies that when endpoints within us-east become unhealthy
 traffic should failover to endpoints in any zone or sub-zone within eu-west
 and similarly us-west should failover to us-east.
 ```yaml
  failover:
    - from: us-east
      to: eu-west
    - from: us-west
      to: us-east
 ```
 Locality load balancing settings.
    Protobuf type istio.networking.v1alpha3.LocalityLoadBalancerSetting