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
It seems that currently the max Replica is used to determine how many resources each Kubernetes resource needs and than that is simply summed. This leaves the headroom for all Deployments to do simultaneous rollouts, which is a very conservative approach.
I would like a parameter like --max-simultaneous-rollouts n to tell the summing to only consider max replicas for the biggest n Resources.
As it doesn't seem like this is beeing maintained I created my own fork, in which I plan to implement this.
Should I be mistaken, please let me know and I'll create pull requests.
The text was updated successfully, but these errors were encountered:
It seems that currently the max Replica is used to determine how many resources each Kubernetes resource needs and than that is simply summed. This leaves the headroom for all Deployments to do simultaneous rollouts, which is a very conservative approach.
I would like a parameter like
--max-simultaneous-rollouts n
to tell the summing to only consider max replicas for the biggestn
Resources.As it doesn't seem like this is beeing maintained I created my own fork, in which I plan to implement this.
Should I be mistaken, please let me know and I'll create pull requests.
The text was updated successfully, but these errors were encountered: