Update latency profile observer, controller to fix problem where re-activating empty profile retained old config

Signed-off-by: Swarup Ghosh <[email protected]>

Author: swghosh

pkg/operator/configobservation/configobservercontroller/observe_config_controller.go

@@ -145,11 +145,13 @@ func NewConfigObserver(
 			network.ObserveServicesNodePortRange,
 			nodeobserver.NewLatencyProfileObserver(
 				node.LatencyConfigs,
-				nodeobserver.NewSuppressConfigUpdateUntilSameProfileFunc(
-					operatorClient,
-					kubeInformersForNamespaces.ConfigMapLister().ConfigMaps(operatorclient.TargetNamespace),
-					node.LatencyConfigs,
-				),
+				[]nodeobserver.ShouldSuppressConfigUpdatesFunc{
+					nodeobserver.NewSuppressConfigUpdateUntilSameProfileFunc(
+						operatorClient,
+						kubeInformersForNamespaces.ConfigMapLister().ConfigMaps(operatorclient.TargetNamespace),
+						node.LatencyConfigs,
+					),
+				},
 			),
 			proxy.NewProxyObserveFunc([]string{"targetconfigcontroller", "proxy"}),
 			images.ObserveInternalRegistryHostname,

pkg/operator/starter.go

@@ -375,7 +375,7 @@ func RunOperator(ctx context.Context, controllerContext *controllercmd.Controlle
 	latencyProfileController := latencyprofilecontroller.NewLatencyProfileController(
 		operatorClient,
 		operatorclient.TargetNamespace,
-		node.LatencyConfigs,
+		nil, // profile rejection logic is not required for this operator
 		latencyprofilecontroller.NewInstallerRevisionConfigMatcher(
 			kubeInformersForNamespaces.ConfigMapLister().ConfigMaps(operatorclient.TargetNamespace),
 			node.LatencyConfigs,