fix(cstor-volume-mgmt): high cpu usage caused by for {} loop

The commit bd44756 had refactored
the cstor-volume-mgmt code to start the receivers in a for {} loop.
This caused go processes to spin more cpu.

Signed-off-by: kmova <[email protected]>

cmd/cstor-volume-mgmt/controller/start-controller/controller.go

@@ -86,8 +86,8 @@ func StartControllers(kubeconfig string) {
 	cStorVolumeController := volumecontroller.NewCStorVolumeController(kubeClient, openebsClient, kubeInformerFactory,
 		openebsInformerFactory)
 
-	go startSharedInformerFactory(kubeInformerFactory, stopCh)
-	go startExternalVersionsInformerFactory(openebsInformerFactory, stopCh)
+	go kubeInformerFactory.Start(stopCh)
+	go openebsInformerFactory.Start(stopCh)
 
 	// Waitgroup for starting volume controller goroutines.
 	var wg sync.WaitGroup
@@ -103,18 +103,6 @@ func StartControllers(kubeconfig string) {
 	wg.Wait()
 }
 
-func startSharedInformerFactory(factory kubeinformers.SharedInformerFactory, stopCh <-chan struct{}) {
-	for {
-		factory.Start(stopCh)
-	}
-}
-
-func startExternalVersionsInformerFactory(factory informers.SharedInformerFactory, stopCh <-chan struct{}) {
-	for {
-		factory.Start(stopCh)
-	}
-}
-
 // GetClusterConfig return the config for k8s.
 func getClusterConfig(kubeconfig string) (*rest.Config, error) {
 	var masterURL string