Sync with upstream v1.20.3 #130
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
Cluster Autoscaler 1.20.0
This commit fixes sample manifest of cluster-autoscaler clusterapi provider. (cherry picked from commit a5fee21)
…-release-1.20 Backport of kubernetes#3805: Fix cluster-autoscaler clusterapi sample manifest
…lps load balancer to remove the node from healthy hosts (ALB does have this support). This won't fix the issue of 502 completely as there is some time node has to live even after cordoning as to serve In-Flight request but load balancer can be configured to remove Cordon nodes from healthy host list. This feature is enabled by cordon-node-before-terminating flag with default value as false to retain existing behavior.
cherry pick kubernetes#3649 - Adding functionality to cordon the node before destroying it.
While this was previously effectively limited to 50, `DescribeAutoScalingGroups` now supports fetching 100 ASG per calls on all regions, matching what's documented: https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_DescribeAutoScalingGroups.html ``` AutoScalingGroupNames.member.N The names of the Auto Scaling groups. By default, you can only specify up to 50 names. You can optionally increase this limit using the MaxRecords parameter. MaxRecords The maximum number of items to return with this call. The default value is 50 and the maximum value is 100. ``` Doubling this halves API calls on large clusters, which should help to prevent throttling.
Refactor to allow for optimisation
The pricing json for us-east-1 is currently 129MB. Currently fetching this into memory and parsing results in a large memory footprint on startup, and can lead to the autoscaler being OOMKilled. Change the ReadAll/Unmarshal logic to a stream decoder to significantly reduce the memory use.
Co-authored-by: Guy Templeton <guyjtempleton@googlemail.com>
…pick-of-#3999-kubernetes#4199-upstream-cluster-autoscaler-release-1.20 Automated cherry pick of kubernetes#3999 kubernetes#4127 kubernetes#4199 upstream cluster autoscaler release 1.20
…packet-fix Cloud provider[Packet] fixes
Backport Merge pull request kubernetes#4274 to upstream/cluster-autoscaler-release-1.20
…s unready. Deprecated LongNotStarted In cases where node n1 would: 1) Be created at t=0min 2) Ready condition is true at t=2.5min 3) Not ready taint is removed at t=3min the ready node is counted as unready Tested cases after fix: 1) Case described above 2) Nodes not starting even after 15mins still treated as unready 3) Nodes created long ago that suddenly become unready are counted as unready.
Signed-off-by: Sylvain Rabot <sylvain@abstraction.fr>
Cherry pick 535a212 onto 1.20 - Fix logging level
Cherry-pick kubernetes#4130: dont proactively decrement azure cache for unregistered nodes
…ick-of-#3924-upstream-cluster-autoscaler-release-1.20 Automated cherry pick of kubernetes#3924: Fix bug where a node that becomes ready after 2 mins can be
…ed to 1.20 in kubernetes#4319 The backport included unit tests using a function that changed signature after 1.20. This was not detected before merging because CI is not running correctly on 1.20.
Cluster Autoscaler: fix unit tests after kubernetes#3924 was backported to 1.20 in kubernetes#4319
Fix 1.20 build after Azure cherry-picks
Cluster Autoscaler 1.20.1
…migration enabled) Signed-off-by: ialidzhikov <i.alidjikov@gmail.com>
…pick-of-#4539-upstream-cluster-autoscaler-release-1.20 [release-1.20] Automated cherry pick of kubernetes#4539: Add `--feature-gates` flag to support scale up on volume
…r-release-1.20-aws-instance-update-02-06-2022 CA - AWS Cloud Provider - 1.20 Static Instance List Update 02-06-2022
…r-release-1.20.3 Cluster Autoscaler - 1.20.3 release
gardener-robot
added
needs/review
|
|
gardener-robot-ci-3
added
the
reviewed/ok-to-test
gardener-robot-ci-1
added
needs/ok-to-test
…62298a730415c5d2ab72607ef6adadd6304d (e3de622)
gardener-robot-ci-3
added
reviewed/ok-to-test
|
/invite @ialidzhikov |
gardener-robot
added
reviewed/lgtm
gardener-robot
added
the
status/closed
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.
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: