Joachim
Joachim
/retest Failure doesn't look related ([here](https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/client-go/1157/pull-client-go-build/1565068207629275136/build-log.txt)): > plugin/pkg/client/auth/exec/metrics.go:21:2: package io/fs is not in GOROOT (/usr/local/go/src/io/fs)
I'd like to make sure if I understand the issue correctly. The goal here is to support Java / Golang applications (or at least some of their configurations). And keeping...
#5029 is another issue about improving support for Java
I think I saw this problem some tie ago. When I was implementing [OOM tests for VPA](https://github.com/kubernetes/autoscaler/blob/de59b91dc4e885e4fb926ad63d41f15113fa08b8/vertical-pod-autoscaler/e2e/v1/full_vpa.go#L249). Test didn't work if memory usage grew too quickly - pods were OOMing...
I think I saw this problem some tie ago. When I was implementing [OOM tests for VPA](https://github.com/kubernetes/autoscaler/blob/de59b91dc4e885e4fb926ad63d41f15113fa08b8/vertical-pod-autoscaler/e2e/v1/full_vpa.go#L249). Test didn't work if memory usage grew too quickly - pods were OOMing...
/remove-lifecycle stale
If we implemented #5237 then you could set N=1 and you would get this behavior. Or is there a difference I missed?
VPA will set recommendation after it calculates it. If everything is configured correctly (VPA is pointing to an existing controller, there are pods running in the controller, pods are reporting...
Looks like a log indicating some problem with getting metrics I can't say anything more just from that, pleas provide some more details.
That's a good point. We're setting `Auto` as default [here](https://github.com/kubernetes/autoscaler/blob/b553a7a300fd2a7e0f728612f97c5669f94ab8d5/vertical-pod-autoscaler/pkg/admission-controller/resource/vpa/handler.go#L95) and we've been doing that for a long time (blame says the line is from 2020 but from PR it...