-
Notifications
You must be signed in to change notification settings - Fork 4k
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 for inPlaceVerticalScaling - Timelines ?? #6680
Comments
Its still in alpha and is likely blocked because it wasn't designed into the kubelet state loop: kubernetes/kubernetes#116971 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/area vertical-pod-autoscaler |
closing as duplicate of #4016 which you can track the progress in. My gut feeling is that this will take a while, given that the feature is still in alpha state. |
@voelzmo: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Vertical Pod Autoscaling
I've read the various issues and support tickets on this but I'm kind of wanting to know how long before VPA supports this awesome feature. Where I currently work this would be a massive help to us.
Our use case for it is that springboot java spikes CPU on startup which leads to cpu throttling which in turn effects startup times. Some of our services read from Kafka and we'd like to scale these to zero and use keda to scale it up when messages arrive on the topic. If we could increase CPU and mem at startup to improve startup times and then reduce it to normal working levels after that then that could possibly lead to cost savings across our estate, well in theory.
The text was updated successfully, but these errors were encountered: