Sync with upstream v1.22.3 #131
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
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.
…pick-of-#3999-kubernetes#4199-upstream-cluster-autoscaler-release-1.22 Automated cherry pick of kubernetes#3999 kubernetes#4199 upstream cluster autoscaler release 1.22
Magnum allows using the microversion string "latest", and it will replace it internally with the highest microversion that it supports. This will let the autoscaler use microversion 1.10 which allows scaling groups to 0 nodes, if it is available. The autoscaler will still be able to use microversion 1.9 on older versions of magnum.
Cherry pick kubernetes#4261 (magnum microversion) to cluster-autoscaler-release-1.22
…packet-fix Cloud provider[Packet] fixes
Backport Merge pull request kubernetes#4274 to upstream/cluster-autoscaler-release-1.22
Signed-off-by: Sylvain Rabot <[email protected]>
Cherry pick 535a212 onto 1.22 - Fix logging level
Cluster Autoscaler 1.22.1
…ist-Update-03-10-21-1.22 CA - AWS - Instance List Update 03-10-21 - 1.22 release branch
…lease-1.22 CA - AWS - Instance List Update 29-10-21 - 1.22 release branch
…nce-types add more azure instance types
…elease-1.22 Cherry-pick kubernetes#4497 onto 1.22 - add more azure instance types
…ist-Update-29-11-21-1.22 Cluster-Autoscaler update AWS EC2 instance types with g5, m6 and r6 - 1.22 release branch
…ist-Update-13-12-21-1.22 CA - AWS Instance List Update - 13/12/21 - 1.22
Cluster Autoscaler 1.22.2
…migration enabled) Signed-off-by: ialidzhikov <[email protected]>
…pick-of-#4539-upstream-cluster-autoscaler-release-1.22 [release-1.22] Automated cherry pick of kubernetes#4539: Add `--feature-gates` flag to support scale up on volume
Fix Azure IMDS Url in InstanceMetadataService initialization
Signed-off-by: Zhecheng Li <[email protected]>
Remove variables not used in azure_util_test
corrected the azure_kubernetes_ercice_pool_test unit test cases involving the changed tag prefix added const aksManagedPoolName attribute to the top of the code and fixed file name sercice -> service added logic for old clusters that still have poolName added legacy tag for poolName Fixed Autoscaling due to VMSS tag prefix issue, added tags for legacy poolName and aksManagedPoolName, and corrected file name sercice->service
…o-cherry-picks Cherry-pick kubernetes#4421, kubernetes#4550 - Azure scale from zero improvements
…x-CherryPick-release-1.22 fix autoscaling due to VMSS tag prefix issue - Cherry Pick into release 1.22
Instead of logging a fatal error, log a standard error and fall back to loading instance types from the static list.
…ease-1.22-aws-fallback CA - AWS Cloud Provider - 1.22 - fix instance type fallback
…r-release-1.22-aws-instance-update-02-06-2022 CA - AWS Cloud Provider - 1.22 Static Instance List Update 02-06-2022
…r-release-1.22.3 Cluster Autoscaler - 1.22.3 release
gardener-robot
added
needs/review
gardener-robot-ci-1
added
reviewed/ok-to-test
|
|
|
/invite @ialidzhikov |
1 similar comment
|
/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: