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 - September/October 2024 #7315

Open
gjtempleton opened this issue Sep 30, 2024 · 9 comments
Open

Cluster Autoscaler Patch Releases - September/October 2024 #7315

gjtempleton opened this issue Sep 30, 2024 · 9 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

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

@apricote
Copy link
Member

apricote commented Oct 1, 2024

All set for area/provider/hetzner Issues or PRs related to Hetzner provider

Thanks for taking care of this 😊

@adrianmoisey
Copy link
Member

/area cluster-autoscaler

@aleksandra-malinowska
Copy link
Contributor

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.

@Shubham82
Copy link
Contributor

/area core-autoscaler
/kind feature

@k8s-ci-robot k8s-ci-robot added 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. labels Oct 1, 2024
@thearchitector
Copy link

Is there an updated timeline here?

@x13n
Copy link
Member

x13n commented Oct 16, 2024

@gjtempleton Please include #7409 if you didn't start the patch release process yet.

@gjtempleton
Copy link
Member Author

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.

@thearchitector
Copy link

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!

@gjtempleton
Copy link
Member Author

Promotion PR is here: kubernetes/k8s.io#7429 (comment)

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

8 participants