Hey Pulumi friends, did anyone face warnings about

client-side throttling

? If yes - How did you get rid of them? I keep getting spammed with messages like this during provisioning of my cluster(s):

Diagnostics:
  pulumi:pulumi:Stack (development-localhost):
    I0602 12:31:12.623746   98885 request.go:665] Waited for 1.044442038s due to client-side throttling, not priority and fairness, request: GET:<https://127.0.0.1:6443/api/v1/namespaces/harbor>
    I0602 12:31:23.024342   98885 request.go:665] Waited for 1.019069815s due to client-side throttling, not priority and fairness, request: GET:<https://127.0.0.1:6443/api/v1/namespaces/minio>
  [..]

I found several reports to delete and/or

chown

the

~/.kube/cache

directory. This did not help for me. Any ideas?

@nice-lizard-13594 this is thrown by your kubernetes cluster, it's not coming from Pulumi. Pulumi is just reporting the api is throttling you

Thanks @billowy-army-68599 - I understand that Pulumi is only forwarding the warning. The Kubernetes documentation about Priority and Fairness states it’s a server-side feature of

kube-apiserver

. The warning explicitly states it is client side throttling not caused by priority and fairness. So it’s not thrown by my cluster. I can’t find any reference to throttling settings for

kubectl

. Does Pulumi use the

kubectl

CLI under the hood? Or does it send requests to the Kubernetes API directly?

It talks directly to the API

You can set burst/qps settings through kube client settings: https://www.pulumi.com/registry/packages/kubernetes/api-docs/provider/#kubeclientsettings

Jeah @sparse-park-68967 that’s exactly what I was looking for. Thank you soooo much. You made my day! 🙏

No worries at all!