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 1.16.5 #2874

Conversation

maximerenou50
Copy link
Contributor

Update Cluster Autoscaler version to 1.16.5

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 2, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign piosz
You can assign the PR to them by writing /assign @piosz in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@maximerenou50
Copy link
Contributor Author

Hello,

Any news on that? Please let me know if I missed something to get a new release, I'm particularly interested in getting that MR into an official release.

Thank you

@piteur
Copy link

piteur commented Mar 5, 2020

🙏 Waiting for that release too, as I'm facing this issue on production right now.
Thanks for your time on that @maximerenou50, perfect timing for us!

Cf: #2851 (comment)

@MaciekPytel
Copy link
Contributor

Similarly to Kubernetes we don't really have any process for triggering a new release. Building a release is a mostly manual process and we release roughly every 2 months or so. The version bump PR is generally done by a person doing the release as part of release process.

Right now we're focusing on getting 1.18 CA in time for Kubernetes release. Changes to scheduler in 1.18 require huge changes to CA and we're racing to implement those in time.
Given the above, the likely timeline for next round of patch releases is around the time of 1.18 release (late March) or as soon as we've managed to build 1.18.0 CA.

@maximerenou50
Copy link
Contributor Author

Hi @MaciekPytel,
Thanks for your feedback. I haven't realized that releases were a manual process (that's unfortunate).
In that case, I don't really have a choice than to wait for a new release of 1.16 to occurs. I will close that PR then and keep an eye on the release.
Cheers

@maximerenou50 maximerenou50 deleted the cluster-autoscaler-1-16-5 branch March 9, 2020 09:40
@2ZZ
Copy link

2ZZ commented Mar 25, 2020

Hi @MaciekPytel, has there been any movement on a 1.16 release now that 1.18 is out? :)
We could really do with this fix.

@MaciekPytel
Copy link
Contributor

cc: @towca - I believe you were planning to prepare patch releases soon? Do you have any particular date in mind?

@towca
Copy link
Collaborator

towca commented Mar 27, 2020

I want to do it on Monday: #2988.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants