<p>I am trying to setup K8S to work with two Windows Nodes (2019). Everything seems to be working well and the containers are working and accessible using k8s service. But, once I introduce configuration for readiness (or liveness) probes - all fails.  The exact error is:</p>
<blockquote>
<p>Readiness probe failed: Get <a href="http://10.244.1.28:80/test.txt" rel="nofollow noreferrer">http://10.244.1.28:80/test.txt</a>: dial tcp 10.244.1.28:80: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.</p>
</blockquote>
<p>When I try the url from k8s <strong>master</strong>, it works well and I get 200. However I read that the kubelet is the one executing the probe and indeed when trying from the Windows Node - it cannot be reached (which seems weird because the container is running on that same node). Therefore I assume that the problem is related to some network configuration.</p>
<p>I have a HyperV with External network Virtual Switch configured. K8S is configured to use flannel overlay (vxlan) as instructed here: <a href="https://learn.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/network-topologies" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/network-topologies</a>.</p>
<p>Any idea how to troubleshoot and fix this?</p>
<p><strong>UPDATE</strong>: providing the yaml:</p>
<pre><code>apiVersion: v1
kind: Service
metadata:
  name: dummywebapplication
  labels:
    app: dummywebapplication
spec:
  ports:
    # the port that this service should serve on
  - port: 80
    targetPort: 80
  selector:
    app: dummywebapplication
  type: NodePort
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  labels:
    app: dummywebapplication
  name: dummywebapplication
spec:
  replicas: 2
  template:
    metadata:
      labels:
        app: dummywebapplication
      name: dummywebapplication
    spec:
      containers:
      - name: dummywebapplication
        image: &lt;my image&gt;
        readinessProbe:
          httpGet:
            path: /test.txt
            port: 80
          initialDelaySeconds: 15
          periodSeconds: 30
          timeoutSeconds: 60
      nodeSelector:
        beta.kubernetes.io/os: windows
</code></pre>
<p>And one more update. In this doc (<a href="https://kubernetes.io/docs/setup/windows/intro-windows-in-kubernetes/" rel="nofollow noreferrer">https://kubernetes.io/docs/setup/windows/intro-windows-in-kubernetes/</a>) it is written:</p>
<blockquote>
<p><strong>My Windows node cannot access NodePort service</strong></p>
<p>Local NodePort access from the node itself fails. This is a known
limitation. NodePort access works from other nodes or external
clients.</p>
</blockquote>
<p>I don't know if this is related or not as I could not connect to the container from a different node as stated above. I also tried a service of LoadBalancer type but it didn't provide a different result.</p>

<p>The network configuration assumption was correct. It seems that for 'overlay', by default, the kubelet on the node cannot reach the IP of the container. So it keeps returning timeouts and connection refused messages.</p>

<p>Possible workarounds:</p>

<ol>
<li>Insert an 'exception' into the ExceptionList 'OutBoundNAT' of C:\k\cni\config on the nodes. This is somewhat tricky if you start the node with start.ps1 because it overwrites this file everytime. I had to tweak 'Update-CNIConfig' function in c:\k\helper.psm1 to re-insert the exception similar to the 'l2bridge' in that file.</li>
<li>Use '<a href="https://learn.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/network-topologies#flannel-in-host-gateway-mode" rel="nofollow noreferrer">l2bridge</a>' configuration. Seems like '<a href="https://kubernetes.io/docs/setup/windows/#networking" rel="nofollow noreferrer">overlay</a>' is running in a more secured isolation, but l2bridge is not.</li>
</ol>
