feat: make batch size configurable

[Ryu-Z]

feat: make batch size configurable

Description

This change adds a new configuration option max-batch-size that allows users to control the maximum number of pods that can be scheduled in a single batch.
When not set, there is no limit applied.

What this PR does / why we need it

• Makes the batch size limit configurable through a new max-batch-size option.
• Currently the batch size is hardcoded to 40, which may not be optimal for all environments.

Which issue(s) this PR fixes

Fixes #N/A

Special notes for your reviewer

• Added as an optional configuration
• Default behavior remains unchanged when not set
• Added unit tests to verify the functionality

How was this change tested?

• Unit tests added
• Manual testing with different max-batch-size values

Does this PR introduce a user-facing change?

Yes. Adds a new configuration option:

--max-batch-size

[linux-foundation-easycla]

• ❌ The email address for the commit (3ba27c9) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Ryu-Z
Once this PR has been reviewed and has the lgtm label, please assign mwielgus for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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]

Welcome @Ryu-Z!

It looks like this is your first PR to kubernetes-sigs/karpenter 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/karpenter has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Ryu-Z. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.