Skip to content

Use shared informers #5320

@floreks

Description

@floreks

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions