Possibly optimize workers to re-use a common informer across full & partial syncs

Problem

As a part of supporting full sync, a change was introduced to create new informers for each full sync cycle. The underlying principle was to prevent a re-use of worker state when a full sync occurs to prevent issues due to corruption of internal state. As such, full sync was implemented by completing stopping an active worker along with its dependencies (including the k8s informer) and creating them from scratch.

If it is found that K8S informer initialisation is a time-consuming process then a possible optimisation would be to update the logic to re-use informers across workers.

Solution

• Update the logic to re-use a shared informers across workers