Skip to content
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

Extract getting nodes to delete for atomic node groups #7068

Merged
merged 1 commit into from
Jul 31, 2024

Conversation

bskiba
Copy link
Member

@bskiba bskiba commented Jul 18, 2024

Extract logic for overriding nodes to delete when deleting nodes from a ZeroOrMaxNodeScaling node group.
Simplifies the code and removes code duplication.

What type of PR is this?

/kind cleanup
-->

What this PR does / why we need it:

Extract logic for overriding nodes to delete when deleting nodes from a ZeroOrMaxNodeScaling node group.
Simplifies the code and removes code duplication.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jul 18, 2024
@k8s-ci-robot k8s-ci-robot added area/cluster-autoscaler size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jul 18, 2024
@bskiba
Copy link
Member Author

bskiba commented Jul 23, 2024

/assign @kawych

Copy link
Contributor

@kawych kawych left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the overall direction, I have just a couple of extra suggestions

cluster-autoscaler/core/static_autoscaler.go Outdated Show resolved Hide resolved
cluster-autoscaler/core/static_autoscaler.go Outdated Show resolved Hide resolved
cluster-autoscaler/core/static_autoscaler_test.go Outdated Show resolved Hide resolved
cluster-autoscaler/core/static_autoscaler.go Outdated Show resolved Hide resolved
@bskiba bskiba force-pushed the cleanup-for-stockout-2 branch from fe4afe4 to b9b7b34 Compare July 29, 2024 09:43
@kawych
Copy link
Contributor

kawych commented Jul 30, 2024

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 30, 2024
Extract logic for overriding nodes to delete when deleting
nodes from a ZeroOrMaxNodeScaling node group.
Simplifies the code and removes code duplication.
@bskiba bskiba force-pushed the cleanup-for-stockout-2 branch from b9b7b34 to 14b3357 Compare July 30, 2024 12:24
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 30, 2024
@bskiba
Copy link
Member Author

bskiba commented Jul 30, 2024

Thanks! Squashed the commits. @aleksandra-malinowska would you be able to take a look and approve if it looks ok?

@aleksandra-malinowska
Copy link
Contributor

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aleksandra-malinowska, bskiba, kawych

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 31, 2024
@kawych
Copy link
Contributor

kawych commented Jul 31, 2024

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 31, 2024
@k8s-ci-robot k8s-ci-robot merged commit 921b399 into kubernetes:master Jul 31, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/cluster-autoscaler cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants