https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
✅ 1
c
its possible upstream added use of the --wait-interval flag to kube-proxy. Did you check the changelog?
s
The error itself is the module is missing. --wait-interval is unrelated (though deprecated apparently)
c
think so?
I never know what iptables flags need what modules to work
s
Added 
CONFIG_NETFILTER_XT_MATCH_STATISTIC
to my kernel and all errors went away at least
c
It looks to me like that option has been required for a long time
s
Hmm OK. Yeah, not sure why it started giving errors now. Just wanted to make you aware of it
c
blame on the related kube-proxy code that uses 
-m statistic
shows it was added by this commit in 2021, and that was just a move from somewhere else. https://github.com/kubernetes/kubernetes/commit/8ef1255cdde2#diff-2ccafd63d57233fd0697b9852514604ab880e29aeb073035765ad7541cad1b35R1642
s
OK. Don't know why it popped up now in that case. Thanks!
c
last change before that touching 
-m statistic
was 10 years ago at which point it was also already there… so yeah I’d say it’s always been required.
Did you upgrade your kernel at the same time?
s
No. Updated k3s and it started giving these errors. Updated kernel + added kernel option above after it happened
c
we haven’t changed anything around kube-proxy in this release, and I am not seeing any related changes upstream. so not sure what to suggest as the cause.
s
No problem! Should it be added to the list of requirements in check-config? Otherwise I think it' all OK
c
yeah probably. I don’t know that the list we have in check-config is super up to date. that script is kinda best-effort. If you are up for opening a PR that’d be appreciated.
s
137 Views
Open in Slack
PreviousNext
Powered by