-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
Update Cluster Autoscaler version to 1.13.0-rc.2 #71452
Update Cluster Autoscaler version to 1.13.0-rc.2 #71452
Conversation
/sig autoscaling |
/hold |
@mwielgus please approve. |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: losipiuk, mwielgus The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -17,7 +17,7 @@ | |||
"containers": [ | |||
{ | |||
"name": "cluster-autoscaler", | |||
"image": "k8s.gcr.io/cluster-autoscaler:v1.12.0", | |||
"image": "k8s.gcr.io/cluster-autoscaler:v1.13.0-rc.2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI, this version of 1.13 is still not built and tagged. is that alright?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is already released.
see http://gcr.io/google-containers/cluster-autoscaler:v1.13.0-rc.2.
I also tried to pull the aliased k8s.gcr.io/cluster-autoscaler:v1.13.0-rc.2 and it worked
@losipiuk I just had 1 comment relating to the version you are updating to. Otherwise LGTM. Feel free to remove hold when you are ready |
/hold cancel |
This PR updates CA version in gce manifests to 1.13.0-rc.2.
We need to merge it during freeze because, Cluster Autoscaler imports large amount of k8s code to simulate scheduler behavior, yet it lives in separate repository. Therefore
we need to build final release candidate just at the end of k8s release cycle.