Change:
the each of service proxy endpoints in the cluster using a http post(protocol=tcp)  and the request MUST be successful. Container will execute curl command to reach the service port within specified max retry limit and MUST result in reporting unique <del> hostnames. </del> <ins> hostnames. This test is marked LinuxOnly it breaks when using Overlay networking with Windows. </ins> release: v1.9 file: test/e2e/common/network/networking.go - testname: Networking, intra pod http, from node codename: '[sig-network] Networking Granular Checks: Pods should function for node-pod <del> communication: udp [NodeConformance] [Conformance]' </del> <ins> communication: udp [LinuxOnly] [NodeConformance] [Conformance]' </ins> description: Create a hostexec pod that is capable of curl to netcat commands. Create a test Pod that will act as a webserver front end exposing ports 8080 for tcp and 8081 for udp. The netserver service proxies are created on specified number

Discussion:
ci-kubernetes-e2e-capz-master-containerd-windows should function for node-pod communication: http [NodeConformance] should function for node-pod communication: udp [NodeConformance] PR merged on April 4th 2022 Discussed at sig-windows triage meeting as well as regular meeting: This test is passing for flannel overlay: and aks-engine: We plan temporary disable this on the CAPZ test suite while we diagnose what is missing. /sig windows /sig networking /cc
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : ### Which jobs are failing? should function for node-pod communication: udp [NodeConformance] ### Since when has it been failing? /sig networking Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig network Did some looking into this and the tests is not deploying a hostprocess pod for Windows: Following the test flow Creates test pods: Then the hostnetwork is set to true but the windows Hostprocess fields are not set:
This pod being tested has which seems to be causing issues with calico, if I remove that then it works (as the other tests that do pod-pod demonstrate). Once I switched this test to use a hostprocess this test works for on the same host when using Windows overlay. Overlay has this limitation that we have seen before: fail (according to the , it is not mandatory for kubelet to be able to access pods on a different node).
My thoughts are we should disable these two tests for 1.24 because they are not testing what they should be and it requires some tough changes to the framework to make it work as is. These tests also doesn't make sense for . A example of the changes need to make this partially work on l2bridge but not overlay: