<p>Recently i did install kubernetes using <code>kubeadm</code> on my old dual core AMD machine using bionic ubuntu and lxc.
This is my lxc profile which i found in web:</p>
<pre><code>config:
  limits.cpu: &quot;2&quot;
  limits.memory: 2GB
  limits.memory.swap: &quot;false&quot;
  linux.kernel_modules: nf_conntrack_ipv4,ip_tables,ip6_tables,netlink_diag,nf_nat,overlay,br_netfilter
  raw.lxc: &quot;lxc.apparmor.profile=unconfined\nlxc.cap.drop= \nlxc.cgroup.devices.allow=a\nlxc.mount.auto=proc:rw
    sys:rw&quot;
  security.nesting: &quot;true&quot;
  security.privileged: &quot;true&quot;
description: LXD profile for Kubernetes
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic
  root:
    path: /
    pool: default
    type: disk
name: k8s
used_by:
 - /1.0/containers/kmaster1
 - /1.0/containers/kworker1
</code></pre>
<p>And i did run:</p>
<pre><code># mount --make-rshared /
# lxc config device add &quot;kmaster1&quot; &quot;kmsg&quot; unix-char source=&quot;/dev/kmsg&quot; path=&quot;/dev/kmsg&quot;
# lxc config device add &quot;kworker1&quot; &quot;kmsg&quot; unix-char source=&quot;/dev/kmsg&quot; path=&quot;/dev/kmsg&quot;
</code></pre>
<p>The <code>kube-proxy</code> couldn't run because of this error message:</p>
<pre><code>write /sys/module/nf_conntrack/parameters/hashsize: operation not supported
</code></pre>
<p>So i did fix it by editing <code>kube-proxy</code> config and set connection tracking to zero.
After that i did deploy <code>flannel</code> as cni.
my pods can't access to default cluster IP 10.96.0.1 now, But the service is there:</p>
<pre><code>#kubectl describe svc kubernetes
</code></pre>
<pre><code>Name:              kubernetes
Namespace:         default
Labels:            component=apiserver
                   provider=kubernetes
Annotations:       &lt;none&gt;
Selector:          &lt;none&gt;
Type:              ClusterIP
IP Families:       &lt;none&gt;
IP:                10.96.0.1
IPs:               10.96.0.1
Port:              https  443/TCP
TargetPort:        6443/TCP
Endpoints:         10.46.157.182:6443
Session Affinity:  None
Events:            &lt;none&gt;
</code></pre>
<p>May disabling connection tracking makes issue and there's using <code>NAT</code>, i don't know.
Any idea to fix it?</p>

Vahid Alimohamadi
<p>I fixed that in two steps:
first I did make change the <code>kube-proxy</code> config to it's default.
Then i did write to <strong>HOST</strong>'s <code>/sys/module/nf_conntrack/parameters/hashsize</code> the hash size which needed by kube-proxy manually. Then delete kube-proxy pods and let it's deployment to create theme again automatically.
The main problem is <code>Flannel</code> configuration. flannel deployment doesn't looks for my cluster default ip range and set it's ip range <code>10.244.0.0/16</code>
So i did edit it's configuration and change that to my range:</p>
<pre><code>kubectl edit cm -n kube-system kube-flannel-cfg
</code></pre>
<p>And again, delete all flannel pods and let it's deployment to create them again automatically.</p>
<p>Now my pod has access to kubernetes default clusterIP service.</p>
