<p>I have kubernetes 1.17.4 running and Windows nodes joined to it. Overlay networking working fine in accessing all services within Kubernetes, the only problem is windows containers can not access <code>https://kubernetes</code>, connection fails on TCP level. </p>

<pre><code>gregory@master1:~$ k get nodes -o wide
NAME         STATUS   ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                    KERNEL-VERSION     CONTAINER-RUNTIME
master1      Ready    master   23d   v1.17.4   10.0.0.4      &lt;none&gt;        Ubuntu 18.04.4 LTS          5.0.0-1035-azure   docker://19.3.6
winworker1   Ready    &lt;none&gt;   39h   v1.17.4   10.0.0.5      &lt;none&gt;        Windows Server Datacenter   10.0.18363.720     docker://19.3.5

gregory@master1:~$ k get svc --all-namespaces
NAMESPACE      NAME                    TYPE           CLUSTER-IP     EXTERNAL-IP               PORT(S)                  AGE
default        kubernetes              ClusterIP      10.96.0.1      &lt;none&gt;                    443/TCP                  23d
kube-logging   elasticsearch-service   ExternalName   &lt;none&gt;         utilityvm.kubernetes.my   &lt;none&gt;                   12h
kube-logging   kibana                  NodePort       10.104.70.48   &lt;none&gt;                    5601:8080/TCP            3d13h
kube-system    kube-dns                ClusterIP      10.96.0.10     &lt;none&gt;                    53/UDP,53/TCP,9153/TCP   23d

</code></pre>

<p>Flannel is installed in VXLAN mode.</p>

<p>Networking working fine, for example below is Kibana pod running on Linux node and I can connect to it from Windows node but the same communication to API server fails. The same connection to Kube-DNS succeeds</p>

<pre><code>gregory@master1:~$ k get pods -o wide
NAME                            READY   STATUS    RESTARTS   AGE   IP            NODE         NOMINATED NODE   READINESS GATES
win-webserver-fffd4486f-4thjw   1/1     Running   4          22h   10.244.1.95   winworker1   &lt;none&gt;           &lt;none&gt;
win-webserver-fffd4486f-m58l6   1/1     Running   4          41h   10.244.1.97   winworker1   &lt;none&gt;           &lt;none&gt;

gregory@master1:~$ k get pod kibana-7b8b6965d-gqq6q -n kube-logging -o wide
NAME                     READY   STATUS    RESTARTS   AGE   IP            NODE      NOMINATED NODE   READINESS GATES
kibana-7b8b6965d-gqq6q   1/1     Running   0          34m   10.244.0.61   master1   &lt;none&gt;           &lt;none&gt;

gregory@master1:~$ k exec win-webserver-fffd4486f-4thjw -- powershell \(test-netconnection 10.244.0.61 -port 5601\) \| select TcpTestSucceeded     

TcpTestSucceeded
----------------
            True


gregory@master1:~$ k exec win-webserver-fffd4486f-4thjw -- powershell \(test-netconnection 10.96.0.1 -port 443\) \| select TcpTestSucceeded  
WARNING: TCP connect to (10.96.0.1 : 443) failed
WARNING: Ping to 10.96.0.1 failed with status: TimedOut

TcpTestSucceeded
----------------
           False


gregory@master1:~$ k exec win-webserver-fffd4486f-4thjw -- powershell \(test-netconnection 10.96.0.10 -port 53\) \| select TcpTestSucceeded

TcpTestSucceeded
----------------
            True



</code></pre>

Gregory Suvalian
<p>Bug in Kubernetes 1.17.4, fixed in 1.18 per <a href="https://github.com/rancher/rancher/issues/20968" rel="nofollow noreferrer">https://github.com/rancher/rancher/issues/20968</a></p>
