-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Backport patch for early abort on ASGs to cluster autoscaler 1.18.3 #4492
Backport patch for early abort on ASGs to cluster autoscaler 1.18.3 #4492
Conversation
1.18: Ensure only capacity is changed when PUT Azure VMSS
Signed-off-by: Jiaxin Shan <[email protected]>
Properly propagate scale-up failures in scale sets.
Cherry pick kubernetes#2929 kubernetes#2931 to 1.18
Cluster Autoscaler 1.18.1
caches after async PUT succeeds.
CA 1.18: Ensure VMSS is not under updating before scaling out
CA 1.18: Remove checking for VMSS provisioningState before scaling
Cherry-pick kubernetes#3036: Proactively decrement scale set count during deletion operations
Cherry-pick kubernetes#3019: Correct cloudprovider/azure's GPULabel to "accelerator"
…API version. This change adds detection for an environment variable to specify the group for the clusterapi resources. If the environment variable `CAPI_GROUP` is specified, then it will be used instead of the default. This also decouples the API group from the version and let the latter to be discovered dynamically.
[CA-1.18] kubernetes#2934 cherry-pick: Fixes 2932: let the capi version to be discovered
[CA-1.18] kubernetes#2940 cherry-pick CAPI: Stop panicking in newMachineController
Cherry-pick kubernetes#3141: Avoid sending extra deletion calls for in-progress deletions
[CA-1.18] kubernetes#2983 cherry-pick: ClusterAPI Provider: Provide fake proivder IDs for failed Machines
Fix priority expander falling back to random although higher priority matches
Cherry pick 3308 onto 1.18 - Fix priority expander falling back to random although higher priority matches
…r-delete-fix Remove ScaleDownNodeDeleted status since we no longer delete nodes synchronously
Improve Cluster API tests to work better with constrained resources
Merge pull request kubernetes#3441 from detiber/fixCAPITests
…8' into cherry-pick-3570-1.18
Merge pull request kubernetes#3570 from towca/jtuznik/scale-down-after-delete-fix
…32-1.18 Cherry-pick kubernetes#3532 onto 1.18: Azure: support allocatable resources overrides via VMSS tags
Signed-off-by: Marques Johansson <[email protected]>
[cluster-autoscaler] Backport fixes for packet provider to release-1.18
Cluster Autoscaler 1.18.3
Set different hostname label for upcoming nodes -- make change backwards compatible with breaking schedulernodeinfo to schedulerframework change according to kubernetes@73a5cdf
…launch-templates cache ASG InstanceTypes for AWS
…patch-cluster-autoscaler-1.18.3-airbnb2 Backport kubernetes#4073 to 1.18.3
…up-no-capacity early abort if aws node group no capacity
@drmorr0: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: drmorr0 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 |
Whoops, not what I meant to do. |
Upstream PR: #4489