-
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
VPA release 1.0.0 #6113
Comments
Current VPA tests are all green - https://testgrid.k8s.io/sig-autoscaling-vpa |
is there a plan to publish an official helm chart? There is issue open (#5369) with reference to a few of community options, but we are challenged by our security to use 'unofficial' helm chart. |
Like I mentioned in a comment on the issue I think we can accept contributions but don't have capacity to maintain them. As far as I know none contributed helm charts for VPA specifically (one can use CA helm chart to deploy VPA). |
I created new branch: https://github.com/kubernetes/autoscaler/tree/vpa-release-1.0 BTW we should update release documentation to refer to 1.n instead of 0.n from now on |
Thanks @jbartosik. New images are available in gcr.io/k8s-staging-autoscaling (thanks Joachim for the help there as well). Moving onto the testing portion. |
Ran into #6141 as part of this release |
Tests passing:
|
Image is promoted:
|
I think we have to backport #6151 into vpa-release-1.0 branch If seems good then I will open a PR for it. |
@Shubham82 seems totally reasonable, sgtm |
Ran tests again in a new
|
Thanks @raywainman, will raise PR soon. |
Fixed it here: #6160 |
hi all! |
Yes, we're going to. It's taking a bit longer than I expected, sorry about that. |
Apologies for the delay here team. I've compiled the following release notes: What's Changed
Full Changelog@jbartosik can you please help me with the remaining steps in https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/RELEASE.md#finalize-release? Thanks so much! |
Following instructions in RELEASE.md.
Starting this release as recommended by @jbartosik. This corresponds to the k8s 1.28 release.
Please provide any information that is related to the release:
The text was updated successfully, but these errors were encountered: