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
I've tried editing the systemd unit file for kube-proxy to include --conntrack-max-per-core=0 which according to the kube-proxy binary, should disable setting the conntrack value,
root@worker-1:~# kube-proxy --help | grep conntrack
--conntrack-max-per-core int32 Maximum number of NAT connections to track per CPU core (0 to leave the limit as-is and ignore conntrack-min). (default 32768)
--conntrack-min int32 Minimum number of conntrack entries to allocate, regardless of conntrack-max-per-core (set conntrack-max-per-core=0 to leave the limit as-is). (default 131072)
but this setting seems to be ignored and it tried to write to the file anyway.
The text was updated successfully, but these errors were encountered:
I'm following Kubernetes the hard way and made it all the way to configuring the worker nodes: https://github.com/kelseyhightower/kubernetes-the-hard-way/blob/master/docs/09-bootstrapping-kubernetes-workers.md#start-the-worker-services
At this point, the kube-proxy service fails because
which led me to your guide here.
I have added
to my worker node, and
conntrack -L
yields output.On the host machine I can
ls /proc/sys/net/netfilter/nf_conntrack_max
and the file is there.And yet the kube-proxy service still fails because it cannot find this file. Any advice?
edit: on the worker node this is
lsmod | grep conntrack
outputI've tried editing the systemd unit file for kube-proxy to include
--conntrack-max-per-core=0
which according to the kube-proxy binary, should disable setting the conntrack value,but this setting seems to be ignored and it tried to write to the file anyway.
The text was updated successfully, but these errors were encountered: