You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 16, 2020. It is now read-only.
I've added a compatibility nf_conntrack_ipv4 module to the Container Linux kernel, which will be included in the next alpha release. Thanks for reporting!
Activity
dm0- commentedon Oct 26, 2018
What is actually failing? It looks okay if I run
ipvsadm
directly.The
nf_conntrack_ipv4
modules isn't supposed to exist since torvalds/linux@a0ae256.bgilbert commentedon Oct 26, 2018
If for some reason you need to load the module directly,
modprobe nf_conntrack
should be sufficient in 4.19.ijl commentedon Oct 26, 2018
The error is kube-proxy failing to run in ipvs mode due to a check for nf_conntrack_ipv4 specifically (https://github.com/kubernetes/kubernetes/blob/6a8a8597f5bf4de29b7b88384529188df0b71337/pkg/util/ipvs/ipvs.go#L70-L77). So agreed this is an issue with kubernetes and not coreos. Thank you for looking into it.
bgilbert commentedon Oct 26, 2018
Okay, thanks for the info. I'm looking at working around this in Container Linux.
ijl commentedon Oct 26, 2018
@bgilbert it runs while falling back to using iptables. More on the kubernetes issue: kubernetes/kubernetes#70304
bgilbert commentedon Oct 27, 2018
I've added a compatibility
nf_conntrack_ipv4
module to the Container Linux kernel, which will be included in the next alpha release. Thanks for reporting!