-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: When targetRef is a Rollout, VerticalPodAutoscalerCheckpoint history is reset during deployment #6730
Comments
Yeah, so deleting the VPACheckpoints is 100% related to what I described in #5598:
Hope that explains it a bit. In general, it seems that the way how |
/remove-kind bug |
Thanks for the explanation! It seems to me like it would work if VPA treated a |
Which component are you using?:
vertical-pod-autoscaler
What version of the component are you using?:
Component version: 1.0.0
What k8s version are you using (
kubectl version
)?:1.29.1
kubectl version
OutputWhat environment is this in?:
EKS
What did you expect to happen?:
I expect the VPA to retain the history from earlier versions of the same Rollout.
What happened instead?:
VPA deletes the history from the VerticalPodAutoscalerCheckpoint during deployment of a new version using Argo Rollouts, which often means that the memory target is initially set to low which causes unnecessary OOM situations.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
This may be related to the issue mentioned in #5598.
The text was updated successfully, but these errors were encountered: