-
Notifications
You must be signed in to change notification settings - Fork 347
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
proposal: LoadbalancingPolicy #1105
Comments
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
should we provide the global locadbalancing policy in envoyproxy API? |
+1 to adding a global policy in |
* Allows the user to configure a global load balancing strategy for the envoy proxy data plane ``` apiVersion: config.gateway.envoyproxy.io/v1alpha1 kind: EnvoyProxy metadata: name: set-lb-strategy spec: traffic: loadBalancer: strategy: LeastRequest ``` * Sets the default load balancing strategy to `LeastRequest` which will internally set the `WeightedLeastReqquest` knob in Envoy * Relates to envoyproxy#1256 allowing the user to fall back to `ClusterIP` style loadbalancing * Relates to envoyproxy#1105 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/load_balancers#weighted-least-request Relates to envoyproxy#1105 Relevant now that we are introducing multiple endpoints with envoyproxy#1494 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/load_balancers#weighted-least-request Relates to #1105 Relevant now that we are introducing multiple endpoints with #1494 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
Relates to envoyproxy#1105 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
Relates to envoyproxy#1105 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
* Add LoadBalancer IR to HTTPRoute Relates to #1105 Signed-off-by: Arko Dasgupta <arko@tetrate.io> * bump coverage Signed-off-by: Arko Dasgupta <arko@tetrate.io> --------- Signed-off-by: Arko Dasgupta <arko@tetrate.io>
Fixes: envoyproxy#1105 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
* LoadBalancer in BackendTrafficPolicy Fixes: #1105 Signed-off-by: Arko Dasgupta <arko@tetrate.io> * tests Signed-off-by: Arko Dasgupta <arko@tetrate.io> --------- Signed-off-by: Arko Dasgupta <arko@tetrate.io>
* LoadBalancer in BackendTrafficPolicy Fixes: envoyproxy#1105 Signed-off-by: Arko Dasgupta <arko@tetrate.io> * tests Signed-off-by: Arko Dasgupta <arko@tetrate.io> --------- Signed-off-by: Arko Dasgupta <arko@tetrate.io> Signed-off-by: zirain <zirain2009@gmail.com>
Description:
Allow the user to specify Load Balancing policies to load balance requests from the gateway to the upstream.
[optional Relevant Links:]
Relates to kubernetes-sigs/gateway-api#1778
Currently the requests are being load balanced at an L3 / kube-proxy level since requests are being sent to the Cluster IP of the Service. We need to route to the endpoints directly with #35
The text was updated successfully, but these errors were encountered: