Change:
klog.V(4).Infof("Trying to Apply Policies for service %s", spew.Sdump(svcInfo)) var hnsLoadBalancer *loadBalancerInfo var sourceVip = proxier.sourceVip <del> if containsPublicIP { </del> <ins> if containsPublicIP || containsNodeIP { </ins> sourceVip = proxier.nodeIP.String() } hnsLoadBalancer, err := hns.getLoadBalancer(

Discussion:
What happened: Executing inside a Windows Pod, but get the following msg:  What you expected to happen: Executing inside a Windows Pod, could view: How to reproduce it (as minimally and precisely as possible): Flannel mode to create a Cluster with one control plane (via RKE) and one Windows Node (via ) into the Windows Pod is fine is fine , but get timeout error Anything else we need to know?: Windows workload yaml:Nodes info:  Content of from :More researching:Deploy an Nginx workload with host port exposed, and then create an Endpoint and Service for it, finally access the vip from Windows inside:   Environment: Kubernetes version (use ):Cloud provider or hardware configuration:OS (e.g: ): Linux: Windows: Kernel (e.g. ): Linux: Windows: Install tools: Control plane created via RKE, Windows node created by Kuberentes guide Network plugin and version (if this is a network-related bug): Flannel VxLan
/sig windows
More information If we edit the default kubernetes endpoint to point to the node’s public ip, then works
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
can you provide the Kubernetes version for the windows node? I see platform as linux in your post
Hi , it happens in 1.14, 1.15 and 1.16. You sent us a commit to fix it before. It works well. Hope we can get it fixed in upstream as well.
In which version was it fixed?

The k8s version I use is: windows Server core version: The problem still appears
The fix for the issue above is included in 1.18.1 to help further
But it doesn't work in 1.18.1
Verified in K8s 1.18. It only works in some particular Windows versions. I guess it is a Windows (OS) issue. works. doesn't work. If you are using AWS, please use instead of the current default one . CC
I do n’t think it should be a system problem, I am using Microsoft Windows Server version 1909 [OS build .778]
: we have identified a potential issue in this area last week. In order to make sure we are talking about the same issue, would it be possible to collect some logs using the instructions below, please? an elevated powershell Window on the host and run: wget -o collectlogs.ps1 the same command line, run .collectlogs.ps1 share the resulting logs folder
Here is a link to the issue I mentioned in my previous comment: Though the issue description is different, the end result is the same: is not accessible from within the POD
any news about that? I'm also running into this issue with newer Windows Versions and can't stay on build .1039
: Two fixes were merged to the master branch a couple of weeks ago. kubernetes/kubernetes kubernetes/kubernetes AFAICT there is no kubernetes releases yet that include these fixes, but I am expecting the next v1.19.x to include these.
and FYI.