kubernetes
Use shared informers
We should investigate the usage of shared informers in order to better handle Dashboard usage in large clusters. Currently, it puts a quite high load on the API server and on views such as workloads (all namespaces) basically might ask for tens of thousands of resources. The biggest issue now is memory usage. Using cache and better optimizing our API structures (less fields) should improve memory consumption significantly.
https://godoc.org/k8s.io/client-go/informers
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
