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

kubectl apply is slow due to client side throttling #1722

Open
Barsonax opened this issue Feb 22, 2025 · 1 comment
Open

kubectl apply is slow due to client side throttling #1722

Barsonax opened this issue Feb 22, 2025 · 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

@Barsonax
Copy link

Barsonax commented Feb 22, 2025

I constantly see these kind of messages when doing kubectl apply -f - --server-side --force-conflicts --prune --applyset=<applyset>:

Waited for 14.1888454s due to client-side throttling, not priority and fairness, request: GET:https:<url>

Likely this is due to having a decent amount of custom CRD's which causes me to hit the client side limit.

I tried to find a way to increase the client limits but these seem to be not configurable. My server can easily handle more (and if not I could simply add more powerful hardware). How to disable or increase this limit when using the cli? Having to wait is annoying and costly. I think its fine to have somewhat conservative limits by default but they should be configurable in a way.

@Barsonax Barsonax added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 22, 2025
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 22, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

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