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
{{ message }}
This repository has been archived by the owner on Mar 26, 2019. It is now read-only.
@ericavonb opening this to track the improvement effort
Operator is making 13-14 requests/s against the API server. 3-4 of those are PUTs i.e. mutating which can cause a lot potentially unneeded etcd and watcher activity.
query sort_desc(sum by (client) (rate(apiserver_request_count[10m])))
I'm not sure what "fixed" is for this issue, but if an investigation could be done on where the activity is coming from and if it is justified, that would be good.
Most of all controllers should have 0 write rate on the api if no one is modifying their core objects. no one should be writing except on external edges. no one should have writes that only change a timestamp, etc.
@ericavonb opening this to track the improvement effort
Operator is making 13-14 requests/s against the API server. 3-4 of those are PUTs i.e. mutating which can cause a lot potentially unneeded etcd and watcher activity.
query
sort_desc(sum by (client) (rate(apiserver_request_count[10m])))
query
sort_desc(sum without (instance,code,type,contentType,job,endpoint,scope,service) (rate(apiserver_request_count{client="service-serving-cert-signer/v0.0.0 (linux/amd64) kubernetes/$Format",verb=~"GET|PUT|POST|UPDATE"}[10m])))
The text was updated successfully, but these errors were encountered: