Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Wrong external interface detection if bridge already configured #80
I have kubernetes cluster with azure vnet cni enabled and after kubelet restart i see the following errors for new pods.
CNI improperly detects external interface
hello, i'm not using acs-engine. I was evaluating Azure vnet CNI for using in our (@giantswarm) installation on Azure. Unfortunately i've already dropped a cluster, but here are the steps that i did.
CoreOS based k8s 1.7.5 with one dhcp NIC (eth0) with private address. Plus for testing i assigned 2 more IP configurations for the VM in Azure portal.
config was default from archive.
Hope this can help.
@r7vme Is it a consistent repro for you?
Based on above, it seems that somehow the cni plugin lost the state and does not remember that the bridge was already created.. Did kubelet crashed or some other error happened in there?