nice-lizard-13594
06/02/2022, 10:49 AMclient-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?billowy-army-68599
nice-lizard-13594
06/02/2022, 11:22 AMkube-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?billowy-army-68599
sparse-park-68967
06/02/2022, 4:14 PMPULUMI_K8S_CLIENT_BURST
and PULUMI_K8S_CLIENT_QPS
environment variablesnice-lizard-13594
06/02/2022, 4:16 PMsparse-park-68967
06/02/2022, 4:17 PM