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
After some investigation it seems like we can stick with the current approach, as the client provided by the manager (see here) already uses a caching mechanism to limit requests to the api server when doing read requests (apparently by using the Watch option, similarly like the dynamic informer does internally).
Also, the time series for the rate of number of requests to the api server for the KLT resources indicates that the caching mechanism by the provided client leads to a manageable rate of requests:
Goal
Use dynamic informers to expose metrics
Can we have it in a separate service?
The text was updated successfully, but these errors were encountered: