-
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
Cluster Autoscaler Patch Releases - September/October 2024 #7315
Comments
All set for
area/provider/hetzner
Thanks for taking care of this 😊 |
/area cluster-autoscaler |
Opened #7316 with ProvisioningRequest v1 CRD (1.31 only, since v1 was introduced in 1.31.0). Probably not strictly necessary as it doesn't introduce any code change and CA doesn't automatically apply CRD, but if someone wants to use the version from the same branch as CA, they'll get burned without it. |
/area core-autoscaler |
Is there an updated timeline here? |
@gjtempleton Please include #7409 if you didn't start the patch release process yet. |
I got around to updating the k/k dependencies in PRs yesterday, but hadn't got the images built and published yet. The cherry-pick needs a quick tweak before it can be merged, should be easy enough to fix up though, so happy to wait until tomorrow for that. To answer your question @thearchitector, I'll get the images built and pushed to staging tomorrow, promotion might take another day depending on review bandwidth. |
Thanks! |
Promotion PR is here: kubernetes/k8s.io#7429 (comment) |
Closing this issue as Releases and release notes are published. /close Thanks @gjtempleton |
@Shubham82: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Hi all, slightly behind schedule, but I'm aiming to cut new Cluster Autoscaler patch releases for 1.28-1.31 within the next week. If there are any bugfix cherry-picks you want included, please prepare the PRs and let me know in the comments.
Tagging cloud provider owners for visibility:
@BigDarkClown
@MorrisLaw
@RainbowMango
@aleksandra-malinowska
@andrewsykim
@apricote
@Bryce-Soghigian
@comtalyst
@cprivitere
@d-mo
@dbonfigli
@deitch
@detiber
@displague
@drmorr0
@ellistarn
@elmiko
@enxebre
@feiskyer
@gjtempleton
@hardikdr
@hello2mao
@jackfrancis
@jayantjain93
@jlamillan
@kevin-wangzefeng
@MaciekPytel
@nilo19
@ringtail
@tallaxes
@tghartland
@towca
@vadasambar
@vishalanarase
@x13n
@yaroslava-serdiuk
The text was updated successfully, but these errors were encountered: