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 for inPlaceVerticalScaling - Timelines ?? #6680

Closed
SteveWoodTi2 opened this issue Apr 3, 2024 · 5 comments
Closed

Support for inPlaceVerticalScaling - Timelines ?? #6680

SteveWoodTi2 opened this issue Apr 3, 2024 · 5 comments
Labels
area/vertical-pod-autoscaler kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@SteveWoodTi2
Copy link

SteveWoodTi2 commented Apr 3, 2024

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.

@SteveWoodTi2 SteveWoodTi2 added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 3, 2024
@Bryce-Soghigian
Copy link
Member

Its still in alpha and is likely blocked because it wasn't designed into the kubelet state loop: kubernetes/kubernetes#116971

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 2, 2024
@adrianmoisey
Copy link
Member

/area vertical-pod-autoscaler

@voelzmo
Copy link
Contributor

voelzmo commented Jul 24, 2024

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.
/close

@k8s-ci-robot
Copy link
Contributor

@voelzmo: Closing this issue.

In response to this:

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.
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vertical-pod-autoscaler kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

6 participants