Clients can subscribe to Kubernetes events via SharedInformer (JS example)
As various controllers may be watching over a particular resource and each controller has its informer, which maintains its cache, this could lead to synchronization issues. To solve this problem, it is usually recommended to use sharedInformers as they have a shared cache that multiple controllers can use. In
SharedInformers, only one watch is opened on the Kubernetes API server regardless of the number of consumers, without adding extra overhead.