Skip to content
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

Closed
gjtempleton opened this issue Mar 12, 2024 · 6 comments
Closed

Cluster Autoscaler Patch Releases March 2024 #6626

gjtempleton opened this issue Mar 12, 2024 · 6 comments
Labels
area/cluster-autoscaler area/core-autoscaler Denotes an issue that is related to the core autoscaler and is not specific to any provider. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@gjtempleton
Copy link
Member

gjtempleton commented Mar 12, 2024

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

@gjtempleton gjtempleton added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 12, 2024
@avorima
Copy link
Contributor

avorima commented Mar 13, 2024

@gjtempleton is it possible to include backports of #6617 for 1.29 and 1.28?

#6629
#6630

@m-barthelemy
Copy link

Would this release include a fix for this HIGH severity finding? #6279

@gjtempleton
Copy link
Member Author

gjtempleton commented Mar 14, 2024

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.

@gjtempleton
Copy link
Member Author

Releases published and release notes published

/close

@k8s-ci-robot
Copy link
Contributor

@gjtempleton: Closing this issue.

In response to this:

Releases published and release notes published

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cluster-autoscaler area/core-autoscaler Denotes an issue that is related to the core autoscaler and is not specific to any provider. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

5 participants