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

Correct comment for AtomicIncreaseSize method #7106

Merged
merged 1 commit into from
Aug 19, 2024

Conversation

yaroslava-serdiuk
Copy link
Contributor

What type of PR is this?

/kind documentation

Fixes #6856

@k8s-ci-robot k8s-ci-robot added the kind/documentation Categorizes issue or PR as related to documentation. label Aug 1, 2024
@k8s-ci-robot k8s-ci-robot added area/cluster-autoscaler cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Aug 1, 2024
@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Aug 1, 2024
@yaroslava-serdiuk
Copy link
Contributor Author

// - If the method returns nil, it guarantees that delta instances will be added to the node group
// within its MaxNodeProvisionTime. The function should wait until node group size is updated.
// The cloud provider is responsible for tracking and ensuring successful scale up asynchronously.
// - If the method returns nil, it guarantees that either delta instances will be added to the node group
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd remove the phrasing with 'guarantee'.

We can't really have a guarantee that all nodes will register successfully until they do, and caller of this method should be able to handle this case later on (and cluster autoscaler does so, cleaning up the instances as usual).

Maybe sth like:

"AtomicIncreaseSize tries to increase the size of the node group atomically. It returns error if requesting the entire delta fails. The method doesn't wait until the new instances appear.

Implementation is optional. Implementation of this method generally requires external cloud provider support for atomically requesting multiple instances. If implemented, CA will < insert the rest of the description > "

?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

SGTM, done

@aleksandra-malinowska
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 19, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aleksandra-malinowska, yaroslava-serdiuk

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 Aug 19, 2024
@k8s-ci-robot k8s-ci-robot merged commit 305013e into kubernetes:master Aug 19, 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/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Correct comment for AtomicIncreaseSize() method
3 participants