You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calculating the weights for un-weighted backends by the controller would offload some of the work from the sidecar. This weight calculation could potentially be returned in the controller API as implicit_weight
The text was updated successfully, but these errors were encountered:
I think we should avoid any more fields in the JSON schema, especially for things like this. Two options:
We could actually replicate Nginx behavior and avoid the % based weights totally. In other words, you can specify any positive weight for a backend (100, 200, etc.). The controller can distribute the computed weights accordingly across the backends.
We could stick with existing weights (0-1.0]. In this case as well, the controller computes the weights for unweighted backends before passing them on to the sidecar.
Calculating the weights for un-weighted backends by the controller would offload some of the work from the sidecar. This weight calculation could potentially be returned in the controller API as
implicit_weight
The text was updated successfully, but these errors were encountered: