From f5ad58b57b36599efb7da32e6107068b84efa42f Mon Sep 17 00:00:00 2001 From: Dan Winship Date: Sat, 19 Feb 2022 11:50:53 -0500 Subject: [PATCH] Only log full iptables-restore input at V(9) In large clusters, the iptables-restore input will be tens of thousands of lines long, and logging it at V(5) essentially means that "kube-proxy -v=5" cannot be used in such clusters to see _other_ things that get logged at V(5), because logs will get rolled over far too quickly. So bump the full-rules logging output down to V(9). --- pkg/proxy/iptables/proxier.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkg/proxy/iptables/proxier.go b/pkg/proxy/iptables/proxier.go index d0af939db76..ed3e1af53b9 100644 --- a/pkg/proxy/iptables/proxier.go +++ b/pkg/proxy/iptables/proxier.go @@ -1522,7 +1522,7 @@ func (proxier *Proxier) syncProxyRules() { proxier.iptablesData.Write(proxier.natChains.Bytes()) proxier.iptablesData.Write(proxier.natRules.Bytes()) - klog.V(5).InfoS("Restoring iptables", "rules", proxier.iptablesData.Bytes()) + klog.V(9).InfoS("Restoring iptables", "rules", proxier.iptablesData.Bytes()) err = proxier.iptables.RestoreAll(proxier.iptablesData.Bytes(), utiliptables.NoFlushTables, utiliptables.RestoreCounters) if err != nil { if pErr, ok := err.(utiliptables.ParseError); ok {