Comment # 33 on bug 1171770 from Martin Weiss

Quick update on the testing I have done.

1. installed server and enabled IP forwarding
2. verified that the following gives 1 for all:

for FILE in $(sudo find /proc -iname forwarding); do echo $FILE; sudo cat
$FILE; done

3. run skuba to deploy first master:

cd
skuba cluster init caasp --control-plane caasp-api.suse
cd caasp
sed -i 's#podSubnet:.*#podSubnet: 10.100.0.0/16#g' kubeadm-init.conf
sed -i 's#serviceSubnet:.*#serviceSubnet: 10.200.0.0/16#g' kubeadm-init.conf
SERVER=caasp-master-01; skuba node bootstrap $SERVER --sudo --target
$SERVER.suse --user caaspadm -v5 2>&1|tee $SERVER.log

4. verify right after skuba deployment is finished

for FILE in $(sudo find /proc -iname forwarding); do echo $FILE; sudo cat
$FILE; done

-> all 1 - but not yet any cilium or lxc0502ff45e5f9.. network

5. wait a bit and then test again

for FILE in $(sudo find /proc -iname forwarding); do echo $FILE; sudo cat
$FILE; done

/proc/sys/net/ipv4/conf/all/forwarding
1
/proc/sys/net/ipv4/conf/cilium_health/forwarding
1
/proc/sys/net/ipv4/conf/cilium_host/forwarding
1
/proc/sys/net/ipv4/conf/cilium_net/forwarding
1
/proc/sys/net/ipv4/conf/cilium_vxlan/forwarding
1
/proc/sys/net/ipv4/conf/default/forwarding
1
/proc/sys/net/ipv4/conf/eth0/forwarding
0
/proc/sys/net/ipv4/conf/lo/forwarding
0
/proc/sys/net/ipv4/conf/lxc0502ff45e5f9/forwarding
1
/proc/sys/net/ipv4/conf/lxc338fd9c772fe/forwarding
1
/proc/sys/net/ipv4/conf/lxc44ad1805e489/forwarding
1
/proc/sys/net/ipv4/conf/lxc45fc97ce17fc/forwarding
1
/proc/sys/net/ipv4/conf/lxc5c407b7c307a/forwarding
1
/proc/sys/net/ipv4/conf/lxc66ae87817a6a/forwarding
1
/proc/sys/net/ipv4/conf/lxc6f16187be039/forwarding
1
/proc/sys/net/ipv4/conf/lxc927bae83b605/forwarding
1
/proc/sys/net/ipv4/conf/lxc9a7c0128099e/forwarding
1
/proc/sys/net/ipv4/conf/lxcc5c6777e5605/forwarding
1
/proc/sys/net/ipv6/conf/all/forwarding
1
/proc/sys/net/ipv6/conf/cilium_health/forwarding
1
/proc/sys/net/ipv6/conf/cilium_host/forwarding
1
/proc/sys/net/ipv6/conf/cilium_net/forwarding
1
/proc/sys/net/ipv6/conf/cilium_vxlan/forwarding
1
/proc/sys/net/ipv6/conf/default/forwarding
1
/proc/sys/net/ipv6/conf/eth0/forwarding
1
/proc/sys/net/ipv6/conf/lo/forwarding
1
/proc/sys/net/ipv6/conf/lxc0502ff45e5f9/forwarding
1
/proc/sys/net/ipv6/conf/lxc338fd9c772fe/forwarding
1
/proc/sys/net/ipv6/conf/lxc44ad1805e489/forwarding
1
/proc/sys/net/ipv6/conf/lxc45fc97ce17fc/forwarding
1
/proc/sys/net/ipv6/conf/lxc5c407b7c307a/forwarding
1
/proc/sys/net/ipv6/conf/lxc66ae87817a6a/forwarding
1
/proc/sys/net/ipv6/conf/lxc6f16187be039/forwarding
1
/proc/sys/net/ipv6/conf/lxc927bae83b605/forwarding
1
/proc/sys/net/ipv6/conf/lxc9a7c0128099e/forwarding
1
/proc/sys/net/ipv6/conf/lxcc5c6777e5605/forwarding
1


--> so at least in my case the process of the cluster deployment / cilium /
crio etc. start seems to change eth0 and lo to "0" !