k0s
k0s copied to clipboard
k0sproject
Should the NF_CONNTRACK kernel config be part of the pre-flight checks for k0s?
There's some evidence that without it, workers won't work. K0s already includes it in k0s sysinfo and also tries to load nf_conntrack proactively.
Looking at this kube-proxy code, it seems that kube-proxy will error out anyways if nf_conntrack is unavailable. (Note that s.Conntracker is never nil for Linux.)
The issue is marked as stale since no activity has been recorded in 30 days
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
Kube-proxy, cilium and openvSwitch require nf_conntrack.
I don't know any implementation of kube-proxy other than kube-proxy itself or cilium that isn't based on openvSwitch so I think this is a sane thing to do.
The issue is marked as stale since no activity has been recorded in 30 days