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

VPA support for pod-level resource specifications #7571

Open
voelzmo opened this issue Dec 5, 2024 · 1 comment
Open

VPA support for pod-level resource specifications #7571

voelzmo opened this issue Dec 5, 2024 · 1 comment
Labels
area/vertical-pod-autoscaler kind/feature Categorizes issue or PR as related to a new feature.

Comments

@voelzmo
Copy link
Contributor

voelzmo commented Dec 5, 2024

Which component are you using?:
/area vertical-pod-autoscaler

Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
With k8s 1.32, a new feature gate is released in alpha: PodLevelResources, allowing users to specify resources on Pod level instead of on Container level.
More info on how this works in the KEP

Describe the solution you'd like.:
VPA should support this and autoscale Pods instead of individual Containers.
This is just a placeholder/umbrella issue, we need a proper enhancement proposal doc for this.

@voelzmo voelzmo added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 5, 2024
@omerap12
Copy link
Member

omerap12 commented Dec 5, 2024

I’d be happy to open a KEP for this, as I have some ideas to contribute. Specifically, I believe the VPA should support both approaches. That means, if we have PodLevelResources, the scaling should apply at the pod level; otherwise, it should scale at the container level. The main challenge lies in scaling multi-container pods with PodLevelResources. I shared an idea on this topic here: comment.

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.
Projects
None yet
Development

No branches or pull requests

3 participants