-
Notifications
You must be signed in to change notification settings - Fork 42.9k
kubectl api returns Throttling request took message #101631
Copy link
Copy link
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.Categorizes an issue or PR as relevant to SIG API Machinery.sig/instrumentationCategorizes an issue or PR as relevant to SIG Instrumentation.Categorizes an issue or PR as relevant to SIG Instrumentation.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.Categorizes an issue or PR as relevant to SIG API Machinery.sig/instrumentationCategorizes an issue or PR as relevant to SIG Instrumentation.Categorizes an issue or PR as relevant to SIG Instrumentation.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
What happened:
On one of the control-plane node, any kubectl commands take longer time with a log like:
It took long time to respond a kubectl call with this Throttling request took thing.
What you expected to happen:
kubectl API call returns response without error
How to reproduce it (as minimally and precisely as possible):
run any kubectl command
Environment:
kubectl version):