forked from kubernetes/autoscaler
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sync master with upstream #1
Open
cruizen
wants to merge
2,032
commits into
platform9:master
Choose a base branch
from
kubernetes:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
Correct wording would be "above the maximum" which then goes on to explain how the CA handles scaling down a nodepool that is currently above the maxNodes value
…tingOfAKS CA: add artifacts for dev testing of cluster-autoscaler on AKS
Async node group creation
VPA: Add option to set the webhook failurePolicy to Fail
ProvisioningRequest v1 client
azure: document migration to new GPU Node label
Signed-off-by: Omer Aplatony <[email protected]>
…oud-provider-azure chore: defork cloud-provider-azure
Add proactive scaleup
…type The `cx11` server type was deprecated on 2024-06-06 and will be removed from the API on 2024-09-06. Once it is removed, the cluster-autoscaler provider hetzner will not start anymore with the following error message: Failed to get node infos for groups: failed to create resource list for node group draining-node-pool error: failed to get machine type cx11 info error: server type not found As the node pool `draining-node-pool` is not being used anywhere, this commit removes it and the hard coded reference to the deprecated server type.
Fix incorrect wording in FAQ.md
chore: defork labels and taints
This was only used by legacy scale down implementation.
Remove legacy scale down code
This is because it doesn't affect scheduling, but it affect performance of scheduling simulation. It triggered alert from 'overflowing_controllers_count' metric.
Signed-off-by: Omer Aplatony <[email protected]>
…d in last iteration
…Warningf(). Signed-off-by: Omer Aplatony <[email protected]>
…Warningf(). Signed-off-by: Omer Aplatony <[email protected]>
…Warningf(). Signed-off-by: Omer Aplatony <[email protected]>
Bump kubernetes deps to v1.32.0-alpha.0
Fixed External IPs service link.
…oint-input Refactor logging statements in recommender:checkpoint,input
Add support for frequent loops when provisioningrequest is encountered in last iteration
Update k/k dependency to 1.32.0-alpha.2
feat: add webhook labels flag to add labels in VPA admission controller webhook
…arget Refactor logging in recommender, updater, and target components
Remove redundant copy in UpdateProvisioningRequest() method
Refactor logging statements in common,e2e test files
node-group-auto-discovery support for oci
Implemented batch processing for check capacity provisioning class
feat(hetzner): autoscaler includes new provided-by label
Modify scale down set processor to add reasons to unremovable nodes
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 type of PR is this?
/kind cleanup
What this PR does / why we need it:
sync with upstream