-
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 March 2024 #6626
Comments
@gjtempleton is it possible to include backports of #6617 for 1.29 and 1.28? |
Would this release include a fix for this HIGH severity finding? #6279 |
Short answer, unless we have information suggesting this is a high enough risk to work around the fact we vendor it from the upstream k/k repo and it's still to be patched there, no. I've put a bit more context in the original issue. |
Releases published and release notes published /close |
@gjtempleton: 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/test-infra repository. |
I'm planning to cut new Cluster Autoscaler patch releases for 1.26-29 at the end of this week/start of next week. If there are any bugfix cherry-picks you want included, please prepare the PRs and let me know in the comments.
We missed the promotion of 1.26.7, 1.27.6, 1.28.3, and 1.29.1 in the January release cycle, but will be promoting these images which were published to the staging repo 6 weeks ago at the same time.
This will now be the last round of patches for 1.26.
Tagging cloud provider owners for visibility:
@4ND3R50N
@7fELF
@alphajc
@andrewsykim
@Andrius521
@apricote
@ArturasRa
@arunmk
@avorima
@BigDarkClown
@cprivitere
@ctrox
@davidjumani
@dbonfigli
@deitch
@detiber
@displague
@d-mo
@dougsong
@drmorr0
@ellistarn
@elmiko
@enxebre
@ericrrath
@feiskyer
@gajicdev
@gandhipr
@gjtempleton
@happytreees
@hardikdr
@hello2mao
@jackfrancis
@jayantjain93
@jaypipes
@Jeffwan
@jlamillan
@johnl
@jtherin
@kevin-wangzefeng
@LKaemmerling
@louisportay
@MaciekPytel
@marwanad
@MorrisLaw
@mrajashree
@NeilW
@nilo19
@optik-aper
@OriHoch
@pawelkuc
The text was updated successfully, but these errors were encountered: