Kubeinit / kubeinit

Ansible automation to have a KUBErnetes cluster INITialized as soon as possible...

Home Page:https://www.kubeinit.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Question about reaching VMs outside Kubeinit

mmprabhu-coder opened this issue · comments

Hi,
This is more of a question about the virtual networking setup in Kubeinit and not a bug.

I use a test VM, VM-test (IP 172.17.8.101) connected to linux-bridge, virbr2 (IP 172.17.8.1) on the same physical node where the Kubeinit is installed (single controller and single compute node).

I want to ping from Compute-01 to VM-test. I am getting ICMP unreachable errors.

#ping 172.17.8.101 -I enp1s0
PING 172.17.8.101 (172.17.8.101) from 10.0.0.2 enp1s0: 56(84) bytes of data.
From 172.16.0.254 icmp_seq=1 Destination Port Unreachable


#sudo ovs-appctl ovs/route/show
Route Table:
Cached: 172.16.0.254/32 dev br-ex SRC 172.16.0.254 local
Cached: 172.17.8.1/32 dev virbr2 SRC 172.17.8.1 local
Cached: 192.168.121.1/32 dev virbr1 SRC 192.168.121.1 local
Cached: 192.168.122.1/32 dev virbr0 SRC 192.168.122.1 local
Cached: 127.0.0.0/8 dev lo SRC 127.0.0.1 local
Cached: 172.17.8.0/24 dev virbr2 SRC 172.17.8.1 <<<<<<<<<<<<<<<< Expecting to hit this route
Cached: 10.0.0.0/24 dev br-ex GW 172.16.0.1 SRC 172.16.0.254

#sudo netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
10.0.0.0        172.16.0.1      255.255.255.0   UG        0 0          0 br-ex
172.16.0.0      0.0.0.0         255.255.255.0   U         0 0          0 br-ex
172.17.8.0      0.0.0.0         255.255.255.0   U         0 0          0 virbr2

I am able to ping 172.17.8.1 which is virbr2 IP-address.

However, am not able to ping the VM-test which is a VM connected to virbr2. Packets are coming to br-ex but not reach virbr2. Also, ping to external IPs like 8.8.8.8 works. Any help is appreciated.

Thanks,
/M

Was an issue with the rp_filter setting.