-
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 0.14.0 #5851
Comments
The instructions say:
I can see the tests being green here https://k8s-testgrid.appspot.com/sig-autoscaling-vpa#Summary (there's a single flake from actuation suite) but it's really hard to verify what exactly was built. The only thing I'm sure is that we're using golang 1.20.5 which means that #5434 was already included. Luckily this is the last merged PR so it seems we're good to go further. I'll try to see if we can improve (or simply document) matching a test run with the latest included commit. |
I updated version const and created a new release branch. However I ran into trouble during
The same double build is visible for all architectures but the push error is only logged for amd64 (maybe it aborts other pushes). Investigating... |
@voelzmo , are there any special requirements to build the release after your #5746? It seems that the previous release @jbartosik did was prior to this change. |
Ah I think the problem is that I didn't specify a
I guess the fix is to include specification (and deletion) of a builder in the Makefile, to ensure that this is self-contained and not polluted by the env. |
Images were built successfully, thanks @voelzmo for the docker fix :-) One note: during the build my machine ran out of disk so I needed to rerun the whole process after creating more space. Tests passed:
|
Seems like people expect the tag to be on a different commit: We didn't include 96cdd88 and therefore the |
Following instructions in
RELEASE.md.
I'm planning to do the release now, as asked by jbartosik@. It's been a while since K8s 1.27 was releases and IIUC we wanted to release a new minor VPA version around new K8s minor release.
I can also see that golang version has been bumped a few times to address vulnerabilities so I guess it's good to prepare a release for that reason as well.
I don't see any pending PRs which should block the release. In case I missed something, I will simply redo the process.
The text was updated successfully, but these errors were encountered: