# How to Fix "client rate limiter Wait returned an error" in Kubernetes

**URL:** https://community.replicated.com/t/how-to-fix-client-rate-limiter-wait-returned-an-error-in-kubernetes/1511
**Category:** How do I?
**Tags:** support-bundle, kurl
**Created:** [April 30, 2025, 11:45pm UTC](https://community.replicated.com/t/how-to-fix-client-rate-limiter-wait-returned-an-error-in-kubernetes/1511 "2025-04-30T23:45:23Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Dexter\_Yan](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/dexter_yan/32/661_2.png) [@Dexter\_Yan](https://community.replicated.com/u/Dexter_Yan)
#### Post date: [April 30, 2025, 11:45pm UTC](https://community.replicated.com/t/how-to-fix-client-rate-limiter-wait-returned-an-error-in-kubernetes/1511/1 "2025-04-30T23:45:23Z")

</div>

## The Problem

When trying to collect logs or run support bundles in Kubernetes, you might encounter this error:

```auto
failed to get log stream: client rate limiter Wait returned an error: context deadline exceeded

```

This happens when Kubernetes API rate limiting is too restrictive.

## The Root Cause

In some cases, the `kube-proxy-config` ConfigMap had rate limits that were too low:

```yaml
clientConnection:
  burst: 10 # Too low
  qps: 5 # Too low

```

## The Fix

- **Check your current settings** :

```bash
kubectl get configmap kube-proxy-config -n kube-system -o yaml

```

- **Update the ConfigMap** :

```bash
kubectl edit configmap kube-proxy-config -n kube-system

```

- **Increase these values** :

```yaml
clientConnection:
  burst: 100 # Recommended: 100-120
  qps: 20 # Recommended: 20-25

```

## How to Verify

After applying these changes, run your support bundle operation again. The “client rate limiter” error should be gone, and operations should complete successfully.

## Additional Tips

- **EKS-specific** : For AWS EKS clusters, be aware that the control plane has scaling limits:
  - The EKS control plane scales automatically as your cluster grows, but not immediately
  - For more details, see the [AWS EKS Best Practices Guide](https://docs.aws.amazon.com/eks/latest/best-practices/scale-control-plane.html)