allow configuring queries per second/qps

[juliantaylor]

kubectl currently has a hardcoded query per second value of 5. This can make for example pruning resources extremely slow as it will pretty much immediately start throttling.

It would be useful when the queries per second would be configurable so one could for some usecases like apply and pruning increase it.

[seans3]

/sig cli
/area kubectl
/kind feature

[gkarthiks]

/assign

[gkarthiks]

/unassign

[gkarthiks]

@juliantaylor do you have list of commands that you wanted to propose the qps flag for?

for example like,

• apply
• create
• cordon
  etc?

[juliantaylor]

can't it be a generic option that applies to all subcommands like timeouts? all commands should be instantiating the same client-go instance?

If not apply is most relevant as often does a lot of api requests when applying many resources as it needs to get the resources first for patching and then create a patch. And apply --prune does even more requests.

[eddiezane]

This is roughly related to discussions we had around #866.

/priority backlog

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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/test-infra repository.

[k8s-ci-robot]

@Nick-Triller: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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/test-infra repository.

[Nick-Triller]

I believe being able to configure QPS is still a relevant feature and would be helpful for us.