Describe the bug
Describe the bug
When attempting to unpack the Antrea Windows image docker.io/antrea/antrea-windows:latest, I encountered the following error randomly:

unpacking docker.io/antrea/antrea-windows:latest (sha256:9b3c707aabd24d5190afedcd6e6301aa7ffd65a21488550d1b8b771a5c5d7cbb)...
time="2023-10-31T22:55:35-07:00" level=info msg="apply failure, attempting cleanup" error="failed to extract layer sha256:30baeec5d6941292f9e7d22617d5d707b32016e8f936fb75184fa135ac3238bd: hcsshim::ImportLayer failed in Win32: The system cannot find the path specified. (0x3): unknown" key="extract-995477400--Seg sha256:07085b3fdcb4afbf8907934ab6b2483733f12ed6050e5616d44cb9b21d08aaaf"
time="2023-10-31T22:55:37-07:00" level=warning msg="extraction snapshot removal failed" error="snapshot extract-995477400--Seg sha256:07085b3fdcb4afbf8907934ab6b2483733f12ed6050e5616d44cb9b21d08aaaf does not exist: not found" key="extract-995477400--Seg sha256:07085b3fdcb4afbf8907934ab6b2483733f12ed6050e5616d44cb9b21d08aaaf"

To Reproduce
Windows CI pipeline error

We can improve the unit test from below two parts for both linux and windows.

[iptable_rule.go]
[netnat_rule.go]

Describe what you are trying to do
A description of what you are trying to achieve, what you have tried so far and the issues you are facing.
Hi, I want to use an OvS-based network plugin for my k8s cluster so that I can use an SDN controller to control all OvS and realize Service Function Chain forwarding. I have deployed a k8s cluster(v1.16.1 with 1 master node and 1 work node), and applied Antrea (v0.1.1) on the master node. And both node is in Ready status.
My question is: How to find the OvS on the work node and set my SDN controller.

Describe the problem/challenge you have
Currently, we are using various testbeds such as CAPV, Multicast, Multicluster, VMAgent, Kind, and Windows for Antrea CI pipeline. The Kubernetes versions used in these testbeds may not always align with the latest Kubernetes releases. This misalignment can lead to issues, test failures, or missed opportunities to take advantage of new Kubernetes features.

Describe the solution you'd like
We would like to create a long-term tracking mechanism to keep our testbed Kubernetes versions up to date. This involves the following steps:

• Maintain a record of the current Kubernetes version in use for each testbed.
• Periodically check for new Kubernetes releases.
• Plan and execute the upgrade of Kubernetes versions for each testbed as needed.
• Document the process, any issues encountered, and the outcome.

Anything else you would like to add?
It's essential to maintain our testbeds with the latest Kubernetes versions to align with the Kubernetes releases and to provide the best quality testing for Antrea. This long-term tracking task can help us stay on top of Kubernetes updates and ensure our testing environment remains robust and effective.

Describe the problem/challenge you have

Describe the solution you'd like

Anything else you would like to add?

Describe the bug

As of now antrea doesnt support loadBalancerSourceRanges in the antreaProxy. Since this is also not supported in the kube-proxy, we have no way to provdide this to Windows users.

To Reproduce

Similar to kubernetes/kubernetes#120033 ...

Expected

AntreaProxy would fully support the Kubernetes service spec...

Actual behavior

LoadbalancerSourceRanges that are outside of an packet's IP are allowed into antrea clusters where antreaproxy is used.

Note this isnt a HUGE bug b/c alas, even the windows service proxy doesnt yet implement this

QUESTION:

Could this be done by reusing HNS packet filtering from the HNS ACLs ? Or does it require OVS?

aclPolicy := hns.ACLPolicy{
	Type:            hns.ACL,
	Action:          hns.Block,
	Direction:       hns.In,
	RemoteAddresses: loadBalancerSourceRanges
}
```?

Describe the bug
When triggering IPv6 CI tests frequently, pulling docker images could result in a rate limit issue.

To Reproduce
Trigger ipv6 related tests frequently.

Expected
Image should be pulled normally.

Actual behavior
Successfully built e94b32f7fe96
Successfully tagged antrea/openvswitch-debs:antrea-v1.10
Sending build context to Docker daemon 24.06kB

Step 1/11 : FROM ubuntu:22.04 as ovs-debs
toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Additional context
Pulling related images from harbor should be supported to avoid rate limit problem.

Describe the bug
When attempting to unpack the Antrea Windows image docker.io/antrea/antrea-windows:latest, I encountered the following error randomly:

unpacking docker.io/antrea/antrea-windows:latest (sha256:9b3c707aabd24d5190afedcd6e6301aa7ffd65a21488550d1b8b771a5c5d7cbb)...
time="2023-10-31T22:55:35-07:00" level=info msg="apply failure, attempting cleanup" error="failed to extract layer sha256:30baeec5d6941292f9e7d22617d5d707b32016e8f936fb75184fa135ac3238bd: hcsshim::ImportLayer failed in Win32: The system cannot find the path specified. (0x3): unknown" key="extract-995477400--Seg sha256:07085b3fdcb4afbf8907934ab6b2483733f12ed6050e5616d44cb9b21d08aaaf"
time="2023-10-31T22:55:37-07:00" level=warning msg="extraction snapshot removal failed" error="snapshot extract-995477400--Seg sha256:07085b3fdcb4afbf8907934ab6b2483733f12ed6050e5616d44cb9b21d08aaaf does not exist: not found" key="extract-995477400--Seg sha256:07085b3fdcb4afbf8907934ab6b2483733f12ed6050e5616d44cb9b21d08aaaf"
ctr: failed to extract layer sha256:30baeec5d6941292f9e7d22617d5d707b32016e8f936fb75184fa135ac3238bd: hcsshim::ImportLayer failed in Win32: The system cannot find the path specified. (0x3): unknown

To Reproduce
Windows CI pipeline error