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.

Sign up for GitHub

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

Jump to bottom

limit the number of vertical scaling up that could have happened for a certain period of time #341

Open
sanposhiho opened this issue Feb 21, 2024 · 0 comments
Open

limit the number of vertical scaling up that could have happened for a certain period of time #341

sanposhiho opened this issue Feb 21, 2024 · 0 comments
Labels
kind/feature New feature or request priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@sanposhiho
Copy link
Contributor

Scaling down is limited so that it happens once an hour at max.
But, when tortoise suggests scaling up, we always immediately try to scale up Pods for safety for now.
It could cause many restarting happen in a very short period of time.

We know limitting scaling up could be dangerous, but we may want to limit it, to some extent, like scaling down.
@sanposhiho sanposhiho added kind/feature New feature or request priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature or request priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sanposhiho