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
I see lots of "Throttling request took " messages in ODLM pod logs after I deploy ODLM into my kind:
...I0717 23:41:28.212816 1 request.go:655] Throttling request took 1.043109113s, request: GET:https://10.96.0.1:443/apis/flowcontrol.apiserver.k8s.io/v1beta1?timeout=32sI0717 23:41:40.824943 1 request.go:655] Throttling request took 1.039398975s, request: GET:https://10.96.0.1:443/apis/operators.coreos.com/v1alpha1?timeout=32sI0717 23:41:53.430157 1 request.go:655] Throttling request took 1.037565094s, request: GET:https://10.96.0.1:443/apis/flowcontrol.apiserver.k8s.io/v1beta1?timeout=32sI0717 23:42:06.056114 1 request.go:655] Throttling request took 1.046236248s, request: GET:https://10.96.0.1:443/apis/rbac.authorization.k8s.io/v1?timeout=32sI0717 23:42:18.661814 1 request.go:655] Throttling request took 1.03954974s, request: GET:https://10.96.0.1:443/apis/extensions/v1beta1?timeout=32sI0717 23:42:31.265396 1 request.go:655] Throttling request took 1.039429647s, request: GET:https://10.96.0.1:443/apis/pkg.crossplane.io/v1beta1?timeout=32sI0717 23:42:43.872673 1 request.go:655] Throttling request took 1.044666198s, request: GET:https://10.96.0.1:443/apis/configuration.konghq.com/v1?timeout=32s...
It's annoying and a bit nervous. Might be related to the client-go being used in code and its rate limiting stuff. I see some people were discussing this in Kubernetes community and on RedHat bugzilla, but I haven't sorted it out.
What did you expect to happen:
Should not see such many "Throttling request took" messages, could be either toggled or abandoned, or that reflects some issue underlying inside ODLM.
/kind bug
What steps did you take and what happened:
I see lots of "Throttling request took " messages in ODLM pod logs after I deploy ODLM into my kind:
It's annoying and a bit nervous. Might be related to the client-go being used in code and its rate limiting stuff. I see some people were discussing this in Kubernetes community and on RedHat bugzilla, but I haven't sorted it out.
What did you expect to happen:
Should not see such many "Throttling request took" messages, could be either toggled or abandoned, or that reflects some issue underlying inside ODLM.
Environment:
kubectl version
): v1.21.2/etc/os-release
): RHELThe text was updated successfully, but these errors were encountered: