-
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 release - request for cherry-picks #2547
Comments
No bug fixes for magnum, I'm just working on the big upgrade to support magnum's node groups (I'll open an issue). |
Thanks. I will check if any cherry-pick candidates. |
@losipiuk We don't have bug fixes need to be back-ported besides this one. #2435 EKS right now support kubernetes cluster 1.11-1.14. It will take around 2-3 months to support 1.15. Right now, we don't have a version with priority expander support which is critical to our users, especially for spot instance use case. Could we backport this feature? I hope at least we have one version with priority expander support. Seems PR pass all the check. |
I will merge this as it is opt in - and therefore low risk |
@losipiuk Cool. Thank you. I will fix this issue and run some tests. Please hold 1.14 and I will try to make it asap. |
Actually I did not plan to do so. As k8s 1.13 is EOL. If you need that I will do the release by the end of this week. |
Yes please - it will be very helpful for us. Thank you |
https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-1.13.9 :) |
The time has come!
We plan to prepare a set of Cluster Autoscaler patch releases beginning next week. Please issue cherry-picks if you want something in. Just a friendly reminder that as a rule of thumb only bugfixes are cherry-pickable.
cc: @feiskyer, @Jeffwan, @ringtail, @hello2mao, @tghartland
The text was updated successfully, but these errors were encountered: