You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have observed client-side throttling when a large number of pods are running on a spot node, as not all pods get drained within the 2-minute window. Currently, the kubernetes API QPS and burst limits are set to 5 and 10, respectively, and NTH does not provide an option to override these values. Would it make sense for NTH to support configurable overrides for these settings?
INF Waited for 1.160043617s due to client-side throttling, not priority and fairness, request: GET:https://172.20.0.1:443/api/v1/namespaces/test/pods/test-6475fbcfcb-sxd4d
INF Waited for 1.05353185s due to client-side throttling, not priority and fairness, request: GET:https://172.20.0.1:443/api/v1/namespaces/test/pods/test-6475fbcfcb-sgdgd
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We have observed client-side throttling when a large number of pods are running on a spot node, as not all pods get drained within the 2-minute window. Currently, the kubernetes API QPS and burst limits are set to 5 and 10, respectively, and NTH does not provide an option to override these values. Would it make sense for NTH to support configurable overrides for these settings?
https://github.com/kubernetes/client-go/blob/master/rest/config.go#L46-L49
Throttling logs
Beta Was this translation helpful? Give feedback.
All reactions