-
Notifications
You must be signed in to change notification settings - Fork 333
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
Expose config.cluster.v3.Cluster.LeastRequestLbConfig.active_request_bias
in TrafficRoute
policy
#2422
Comments
What situation would benefit from this configuration? Is there some bias value that would be generally beneficial for everyone? |
This would also require exposing the ability to configure weights for individual services. Currently the weights are only set !=1 when there is inter-zone communication and a zone has >1 instances of a particular service. active_request_bias is only valuable when there are endpoints with different weights. The value to the user would be to be able to control the load-balancing behavior to different endpoints with different weights/resources. |
This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. |
|
@lahabana is this something we want in the first version of |
No I related this to the route issue just to keep these kind of features when designing the policy |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
I don't see this being implemented yet, removing stale. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
config.cluster.v3.Cluster.LeastRequestLbConfig.active_request_bias
in Kuma TrafficRoute
policy
config.cluster.v3.Cluster.LeastRequestLbConfig.active_request_bias
in Kuma TrafficRoute
policyconfig.cluster.v3.Cluster.LeastRequestLbConfig.active_request_bias
in TrafficRoute
policy
Summary
I'd like to be able to configure
config.cluster.v3.Cluster.LeastRequestLbConfig.active_request_bias
via a TrafficRoutehttps://www.envoyproxy.io/docs/envoy/latest/api-v3/config/cluster/v3/cluster.proto#envoy-v3-api-msg-config-cluster-v3-cluster-leastrequestlbconfig
https://kuma.io/docs/1.2.2/policies/traffic-route/#usage
The text was updated successfully, but these errors were encountered: