Endpoint configuration

    [ClusterLoadAssignment proto]

    Each route from RDS will map to a single cluster or traffic split across clusters using weights expressed in the RDS WeightedCluster.

    With EDS, each cluster is treated independently from a LB perspective, with LB taking place between the Localities within a cluster and at a finer granularity between the hosts within a locality. The percentage of traffic for each endpoint is determined by both its load_balancing_weight, and the load_balancing_weight of its locality. First, a locality will be selected, then an endpoint within that locality will be chose based on its weight.

    cluster_name

    (, REQUIRED) Name of the cluster. This will be the service_name value if specified in the cluster .

    endpoints

    (endpoint.LocalityLbEndpoints) List of endpoints to load balance to.

    policy

    Load balancing policy settings.

    drop_overloads

    (ClusterLoadAssignment.Policy.DropOverload) Action to trim the overall incoming traffic to protect the upstream hosts. This action allows protection in case the hosts are unable to recover from an outage, or unable to autoscale or unable to handle incoming traffic volume for any reason.

    At the client each category is applied one after the other to generate the ‘actual’ drop percentage on all outgoing traffic. For example:

    overprovisioning_factor

    Read more at and localities.

    endpoint_stale_after

    () The max time until which the endpoints from this assignment can be used. If no new assignments are received before this time expires the endpoints are considered stale and should be marked unhealthy. Defaults to 0 which means endpoints never go stale.

    [ClusterLoadAssignment.Policy.DropOverload proto]

    category

    (, REQUIRED) Identifier for the policy specifying the drop.

    drop_percentage

    (type.FractionalPercent) Percentage of traffic that should be dropped for the category.