One doc tagged with "traffic-manager"

One or more cluster components (kubectl sessions, operators, controllers, CI/CD jobs, etc.) hit the **default client\-side rate\-limiter in client\-go** (QPS = 5, Burst = 10). The client logs messages such as `Waited for <N>s due to client\-side throttling, not priority and fairness` and delays each request until a token is available. Although the API server itself may still have spare capacity, and Priority & Fairness queueing is not the bottleneck, end\-user actions and controllers feel sluggish or appear to “stall”.