kubernetes
kubernetes copied to clipboard
LXD provisioing - Error running ProxyServer" err="write /sys/module/nf_conntrack/parameters/hashsize: operation not supported
Hi Venkat @justmeandopensource
https://github.com/justmeandopensource/kubernetes/tree/master/lxd-provisioning
Looks like issue with this method now. the kube-proxy remains into crashloop and eventually error
root@master:/etc/kubernetes/manifests# kubectl -n kube-system logs kube-proxy-m6xgl
I0823 17:40:52.912090 1 server_linux.go:69] "Using iptables proxy"
I0823 17:40:52.924381 1 server.go:1062] "Successfully retrieved node IP(s)" IPs=["10.2.7.122"]
I0823 17:40:52.932417 1 conntrack.go:59] "Setting nf_conntrack_max" nfConntrackMax=786432
I0823 17:40:52.933129 1 conntrack.go:90] "Setting conntrack hashsize" conntrackHashsize=196608
E0823 17:40:52.933169 1 server.go:558] "Error running ProxyServer" err="write /sys/module/nf_conntrack/parameters/hashsize: operation not supported"
E0823 17:40:52.933190 1 run.go:74] "command failed" err="write /sys/module/nf_conntrack/parameters/hashsize: operation not supported"
I already set value - sysctl -w net.netfilter.nf_conntrack_max=786432. Its not helping at all.
root@master:/etc/kubernetes/manifests# kubectl -n kube-system logs kube-proxy-m6xgl
I0823 17:41:22.913788 1 server_linux.go:69] "Using iptables proxy"
I0823 17:41:22.922042 1 server.go:1062] "Successfully retrieved node IP(s)" IPs=["10.2.7.122"]
I0823 17:41:22.930034 1 conntrack.go:59] "Setting nf_conntrack_max" nfConntrackMax=786432
I0823 17:41:22.931151 1 conntrack.go:90] "Setting conntrack hashsize" conntrackHashsize=196608
E0823 17:41:22.931302 1 server.go:558] "Error running ProxyServer" err="write /sys/module/nf_conntrack/parameters/hashsize: operation not supported"
E0823 17:41:22.931432 1 run.go:74] "command failed" err="write /sys/module/nf_conntrack/parameters/hashsize: operation not supported"
More info - Host ubu 20.04.6 LTS LXD - stable 5.21 I am setting up 1st master node which is running inside ubuntu 22 lxd container.
I am getting node in ready status (I have already deployed flannel network)