-
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
Add information about usage of batch processing for check capacity in FAQ #7282
Conversation
Hi @Duke0404. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
/ok-to-test |
Thanks, @Duke0404 for this PR. |
/lgtm |
@Duke0404, please resolve the merge conflict. |
/lgtm |
cc @aleksandra-malinowska Thanks! |
cc @x13n |
cluster-autoscaler/FAQ.md
Outdated
4. **Batch Timebox**: Set the maximum time in seconds that Cluster Autoscaler will | ||
spend processing CheckCapacity ProvisioningRequests in a single iteration by | ||
setting the following flag in your Cluster Autoscaler configuration: | ||
`--batch-timebox=<timebox>`. The default value is 5m. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see the default changed to 10s in final version, can you please update this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked this in the code and it is 10s.
I missed it, thanks @aleksandra-malinowska
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
/lgtm |
cluster-autoscaler/FAQ.md
Outdated
|
||
#### Enabling Batch Processing | ||
|
||
1. **Cluster Autoscaler Version**: Ensure you are using Cluster Autoscaler version 1.31.1 or later. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.31.1 implies it's going be cherry-picked to 1.31 - I don't think this is likely to happen. We generally don't backport features, only bug-fixes.
I think the first version to have this will be 1.32.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack.
|
||
2. **Feature Flag**: Enable batch processing mode by setting the following flag in your | ||
Cluster Autoscaler configuration: | ||
`--check-capacity-batch-processing=true`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Disabled by default?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, batch processing is disabled by default. Specified in the file.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aleksandra-malinowska, Duke0404 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 |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Adds information about usage of batch processing for check capacity in FAQ
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
cc: @aleksandra-malinowska @kawych