Update Cluster Autoscaler version to 1.3.1-beta.1 #65857
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
release-note-action-required
|
/sig autoscaling |
k8s-ci-robot
requested review from
MaciekPytel
and removed request for
gmarek and
jingax10
k8s-ci-robot
added
the
sig/autoscaling
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aleksandra-malinowska, MaciekPytel 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 |
k8s-ci-robot
added
the
approved
|
Automatic merge from submit-queue (batch tested with PRs 65805, 65811, 65833, 65488, 65857). If you want to cherry-pick this change to another branch, please follow the instructions here. |
k8s-github-robot
pushed a commit
that referenced
this pull request
Aug 2, 2018
…ter-autoscaler-1.3.1 Automatic merge from submit-queue. Update Cluster Autoscaler version to 1.3.1 Cherry-pick of changes from #65857 and #66122. Not automated since we need the change to manifest file, but don't want to introduce beta image on release branch. ```release-note Cluster Autoscaler version updated to 1.3.1. Release notes: https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-1.3.1 Default value for expendable pod priority cutoff in GCP deployment of Cluster Autoscaler changed from 0 to -10. action required: users deploying workloads with priority lower than 0 may want to use priority lower than -10 to avoid triggering scale-up. ``` /cc @MaciekPytel /sig autoscaling
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update Cluster Autoscaler version to 1.3.1-beta.1 and changes the default value for expendable pods priority cutoff in GCP deployment.