The watch cache setup in cache.go uses a MetaNamespaceIndexFunc indexer. As escalator does not list by namespace, only at a cluster level, it is unnecessary. Additionally this introduces a memory leak from client-go with high churn namespaces until kubernetes/84970 is released and escalator uses a client-go version with the patch.
The watch cache setup in cache.go uses a
MetaNamespaceIndexFuncindexer. As escalator does not list by namespace, only at a cluster level, it is unnecessary. Additionally this introduces a memory leak fromclient-gowith high churn namespaces until kubernetes/84970 is released and escalator uses a client-go version with the patch.