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

Ability to configure rate-limit options for nodeclaim reconciles #1717

Open
liafizan opened this issue Sep 26, 2024 · 1 comment
Open

Ability to configure rate-limit options for nodeclaim reconciles #1717

liafizan opened this issue Sep 26, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@liafizan
Copy link

Description

What problem are you trying to solve?
For nodeclaim reconciler
we would like to have ability to customize rate limiting configuration.

We have large clusters with a lot of nodeclaims. Assuming a 1000 node cluster, we would have about 1k nodeclaims and we have 1000 concurrent reconciles configured. With the current configuration we would be making a lot of aws api invocations and eventually slowing down our provisioning.

We would like ability to tune this configuration for our large clusters

How important is this feature to you?
Important as we have been requested by AWS to tune these

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@liafizan liafizan added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 26, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 26, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Karpenter contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants