I applied workaround for https://bugs.launchpad.net/juniperopenstack/+bug/1711274 , and now, am seeing that when a pod got created during that failover time…its vm object did not have link to the vrouter
root@nodec1:~# kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE busybox 0/1 ContainerCreating 0 2m <none> nodek2 nginx1 1/1 Running 0 2m 10.47.255.252 nodek3 root@nodec1:~#
I applied workaround for https:/ /bugs.launchpad .net/juniperope nstack/ +bug/1711274 , and now, am seeing that when a pod got created during that failover time…its vm object did not have link to the vrouter
root@nodec1:~# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
busybox 0/1 ContainerCreating 0 2m <none> nodek2
nginx1 1/1 Running 0 2m 10.47.255.252 nodek3
root@nodec1:~#