mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-07-22 11:21:47 +00:00
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).
This commit is contained in:
parent
e7bae9df81
commit
f5ad58b57b
@ -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 {
|
||||
|
Loading…
Reference in New Issue
Block a user