I have built a kubernetes cluster using kubespray on ubuntu 18.04 and facing dns issue so basically containers cannot communicate through their hostnames. In my routing table even when i am not connected to any network in my windows operating system. Running centos 5.4 why do i have route to 169.254.0.0 although it does not appear in network > ethernet device > route configuration dialog?
'OutDaughtered' Uncle Dale Mills Shares 'Sad' News
If i attempt to connect to. I noted a lot of arp packets asking. After some trials and errors, it appears that such devices are connected as.
I used ovs network and enabled br.
We're seeing some suspicious network activity, and when i was trying to see if it was one particular server of ours i ran a wireshark trace. Manually changing /etc/resolv.conf on the dnsutils pod to use the 10.233.0.3 for the nameserver seemed to correct it for that pod, but how do i fix it for all pods? I get the no dhcp or. I have always noticed an ip something "169.254.x.x"
