Windows server 2016 dhcp not updating dns

looks like below code from file https://github.com/Azure/acs-engine/blob/master/parts/k8s/kuberneteswindowssetup.ps1 creating issue ` Hi @madhanrm & @Jiangtian Li , we are facing issue after restart windows node is unreachable, look like it some code goes into loop, network connectivity goes on and off and after sometime around 30 min node is completely down. Any more ideas as to why pods can't make any outgoing requests? \C:\Program Data\docker\windowsfilter76aaabd774941c332de5bf1c40bbb48c8df0ecaff35441973e9c8174c75885\Utility VM\Files\Windows\Win Sx S\amd64_microsoft-hyper-v-winsock-provider_31bf3856ad364e35_10.0.16299.15_none_fa874cf48b54cc18\wshhyperv.dll: Access is denied. Closing the current window in 5 seconds Hi @madhanrm & @Jiangtian Li , we are facing issue after restart windows node is unreachable, look like it some code goes into loop, network connectivity goes on and off and after sometime around 30 min node is completely down. I've installed the patch, and followed the directions from winter TTr, but my pods still can't resolve DNS names. After installed the patch, my pod (with base image microsoft/dotnet-framework:4.7.1-windowsservercore-1709) failed to pull down the image with the following errors: Failed to pull image "xxxxx": rpc error: code = Unknown desc = failed to register layer: re-exec error: exit status 1: output: remove \? @roycornelissen Can you copy the folder https://github.com/Microsoft/SDN/tree/master/Kubernetes/windows/debug and execute "powershell collectlogs.ps1" I would like to look at the system state first before looking at the traces. Isn't there an official Microsoft solution for this issue? I'm just trying to be thorough in making sure you guys are seeing and fixing/mitigating this very specific DNS issue as well. Another issue was a regression in Windows update in Jan that affects service vip on Windows node and therefore kube-dns. I ask because I've seen a lot of talk about a DNS issue where it works for some short period (15 mins? The problem we are seeing here is that DNS blatantly does not work from the very start at all in Windows containers on 1709 nodes. I'm having the same problem with Azure ACS kubernetes (using Windows server 2016 as a node). If that's so I'd gladly deploy a hybrid with 1 Linux node if I could move forward without hack on the WIndows side. Invoke-Web Request windows10.0-kb4089848-x64_db7c5aad31c520c6983a937c3d531 70e84372b11C:\data\windows10.0-kb4089848-x64_db7c5aad31c520c6983a937c3d53170e84372b11/quiet /norestart Invoke-Web Request windows10.0-kb4089848-x64_db7c5aad31c520c6983a937c3d531 70e84372b11C:\data\windows10.0-kb4089848-x64_db7c5aad31c520c6983a937c3d53170e84372b11/quiet /norestart api Version: apps/v1 kind: Daemon Set metadata: name: network-daemon namespace: kube-system labels: k8s-app: network-daemon spec: selector: match Labels: name: network-daemon-app template: metadata: labels: name: network-daemon-app spec: containers: - name: network-daemon image: your-simple-daemon-image-url node Selector: beta.kubernetes.io/os: windows api Version: apps/v1 kind: Daemon Set metadata: name: network-daemon namespace: kube-system labels: k8s-app: network-daemon spec: selector: match Labels: name: network-daemon-app template: metadata: labels: name: network-daemon-app spec: containers: - name: network-daemon image: your-simple-daemon-image-url node Selector: beta.kubernetes.io/os: windows I'm having the same problem with Azure ACS kubernetes (using Windows server 2016 as a node).

So there will be two patches that fix the two issues separately. Another issue was a regression in Windows update in Jan that affects service vip on Windows node and therefore kube-dns. I looked through #2230 and it does look interesting but its not clear to me that it addresses this issue. This just feels like such a huge roadblocker of an issue that it should be of highest priority to get fixed. I'm still facing this issue without any workaround, using acs-engine to deploy hybrid cluster (2 win, 1 nix) with windows host OS: Server 1709 as per the default latest acs-engine. So, pretty much, some pod names resolve, but I can't resolve services, containers, or FQDNs.

Leave a Reply