fix(NRC): reduce logging for egress cleanup errors

Errors can happen here for a lot of reasons, the user may not have been
running the controller, the definitions may have already been deleted,
the ipset may not be around to be referenced because the user already
cleaned up before.

Reduced the logging to trim user confusion over error statements in the
logs.

Author: aauren

pkg/controllers/routing/network_routes_controller.go

@@ -676,15 +676,19 @@ func (nrc *NetworkRoutingController) setupOverlayTunnel(tunnelName string, nextH
 
 // Cleanup performs the cleanup of configurations done
 func (nrc *NetworkRoutingController) Cleanup() {
+	klog.Infof("Cleaning up NetworkRoutesController configurations")
+
 	// Pod egress cleanup
 	err := nrc.deletePodEgressRule()
 	if err != nil {
-		klog.Warningf("Error deleting Pod egress iptables rule: %s", err.Error())
+		// Changing to level 1 logging as errors occur when ipsets have already been cleaned and needlessly worries users
+		klog.V(1).Infof("Error deleting Pod egress iptables rule: %v", err)
 	}
 
 	err = nrc.deleteBadPodEgressRules()
 	if err != nil {
-		klog.Warningf("Error deleting Pod egress iptables rule: %s", err.Error())
+		// Changing to level 1 logging as errors occur when ipsets have already been cleaned and needlessly worries users
+		klog.V(1).Infof("Error deleting Pod egress iptables rule: %s", err.Error())
 	}
 
 	// delete all ipsets created by kube-router
@@ -713,6 +717,8 @@ func (nrc *NetworkRoutingController) Cleanup() {
 	if err != nil {
 		klog.Warningf("Error deleting ipset: %s", err.Error())
 	}
+
+	klog.Infof("Successfully cleaned the NetworkRoutesController configuration done by kube-router")
 }
 
 func (nrc *NetworkRoutingController) syncNodeIPSets() error {