Mirantis / virtlet

Kubernetes CRI implementation for running VM workloads
Apache License 2.0
743 stars 128 forks source link

Incorrect Routing table(with Missing default route) for route to rest of the cluster #799

Closed kannanvr closed 6 years ago

kannanvr commented 6 years ago

We have spun up the Container with flannel network. It works fine. Across containers, it can communicate with each other. Also, we spun up the VM pod using virtlet, Across VM it is not communicating with each other. We have just used the flannel network. Firewall is not enabled at all.... Kindly provide your suggestions to solve this issue. I am using mirantis/virtlet:latest image

Fedora Image:- https://download.fedoraproject.org/pub/fedora/linux/releases/27/CloudImages/x86_64/images/Fedora-Cloud-Base-27-1.6.x86_64.qcow2

Route on the VM


10.244.1.0/24 dev virtlet-eth0 proto kernel scope link src 10.244.1.7```

Network config 
```[testuser@vm-customer-2-7bb9b896df-mxqkx ~]$ cat /mnt/network-config
version: 1
config:
- mac_address: 0a:58:0a:f4:01:07
  mtu: 1450
  name: virtlet-eth0
  subnets:
  - address: 10.244.1.7
    netmask: 255.255.255.0
    type: static
  type: physical
- destination: 10.244.0.0/16
  gateway: 10.244.1.1
  type: route
- destination: 0.0.0.0/0
  gateway: 10.244.1.1
  type: route
- address:
  - 10.96.0.10
  search:
  - customer-1.svc.cluster.local
  - svc.cluster.local
  - cluster.local
  - ipc3dev.com
  type: nameserver
[testuser@vm-customer-2-7bb9b896df-mxqkx ~]$```