Closed Ladicle closed 3 years ago
I do have the same issue with v0.9.2. I've seen your PR. When will this be released?
This issue persists on 0.9.2 - can we reopen and/or get an idea of when #3903 will be released in VPA?
Hi, I have been getting the same issue. Has there been any fix for this merged into master yet. Does this error persist with other versions of the VPA?
@arnavc1712 @mshade fix for this #3903 is part of 0.10.0 release (you can check blame on this lines)
Which component are you using?: Vertical Pod Autoscaler
What version of the component are you using?:
Component version: 0.9.2
What k8s version are you using (
kubectl version
)?:kubectl version
OutputWhat environment is this in?:
both minikube & on-prem k8s cluster
What did you expect to happen?:
Deployment with limits can be controlled only one resource by VPA.
What happened instead?:
VPA resource only has cpu as a controlledResource, but a vpa-admission-controller sends patch for non controlled resource limits and the value is 0. (like this
{add /spec/containers/0/resources/limits/memory 0}
) For that reason, replicaset-controller getsFailedCreate
error.vpa-admission-controller patch log:
replicaset-controller warning event:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
In this example, cpu is set to controlledResource, but the same thing happens with memory.