-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Release VPA 1.2.0 #7098
Comments
/area vertical-pod-autoscaler |
Built images and ran tests:
|
\o/ |
I see in the docs that "The current default version is Vertical Pod Autoscaler 1.1.2", and can't find any specific changelog for the 1.2.0 release, how is the compatibility? |
Hi @maxboone, The VPA 1.2.0 has not been released yet, it is under process. I think we are left with the last step of release i.e. Finalize release. The text you mentioned above is under the README.md we have to update it also(maybe after release). @raywainman will tell better on this one. PTAL! |
Yep, we are also waiting for the release to be finalized! |
Ah, mentioned it as we use a deployment file from the master / main branch directly in our CI/CD, so it suddenly showed as outdated (but I thought it was released already as it popped up). That's on us! Thanks :) |
Hey all - apologies for the delay, I've been OOO. I'm almost done with the release, they are effectively just formalities at this point:
The process is a bit slow because I need to get someone with the proper rights to help me with the various commands. I'll get this cleaned up and finished asap, sorry for the trouble! |
Tagging commands: At commit dbc88c0:
|
Thanks @raywainman for the information. |
Thank you @raywainman and all other involved maintainers for driving the new release! 🎉 |
Hi @raywainman, what's the minimal k8s version VPA1.2.0 supports? |
I tested it in 1.27 (which is the lowest version supported in GKE currently) but theoretically it should work in 1.25+ as well. |
Please follow instructions in
RELEASE.md and note each
completed step on this issue.
Please provide any information that is related to the release:
ASAP
No
The text was updated successfully, but these errors were encountered: