Skip to content
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

Support an upper bound when updating pods #22

Open
danielblando opened this issue Jun 8, 2023 · 0 comments
Open

Support an upper bound when updating pods #22

danielblando opened this issue Jun 8, 2023 · 0 comments

Comments

@danielblando
Copy link

ZAU currently supports a maxUnavailable and ExponentialFactor params to set how fast we want to update our pods.

We can set maxUnavailable as int or exponential. But that could not be enough in some scenarios where pods scales.
Example: 30 pods running.
If we set the maxUnavailable as 3, when the number of pods grows this number will be obsolete and too small.
If we set the maxUnavailable as 10%, when the number of pods increase a lot (eg:2000), 200 maybe be too fast to update nodes.

It would be nice to have a upper bound limit to not allow the percentage to overcome a certain amount.
One idea is to have something similar to kubernets HPA where you can allow different policies and the behavior which they work
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/

@danielblando danielblando changed the title Support a upper bound when updating pods Support an upper bound when updating pods Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant