Removing docs for Windows hostNetwork support for v1.33 (#49905)

* Removing docs for Windows hostNetwork support for v1.33

* Update content/en/docs/concepts/windows/intro.md

Co-authored-by: Tim Bannister <[email protected]>

---------

Co-authored-by: Tim Bannister <[email protected]>

Author: marosset

content/en/docs/concepts/windows/intro.md

@@ -233,7 +233,7 @@ work between Windows and Linux:
 The following list documents differences between how Pod specifications work between Windows and Linux:
 
 * `hostIPC` and `hostpid` - host namespace sharing is not possible on Windows
-* `hostNetwork` - [see below](#compatibility-v1-pod-spec-containers-hostnetwork)
+* `hostNetwork` - host networking is not possible on Windows
 * `dnsPolicy` - setting the Pod `dnsPolicy` to `ClusterFirstWithHostNet` is
    not supported on Windows because host networking is not provided. Pods always
    run with a container network.
@@ -256,16 +256,12 @@ The following list documents differences between how Pod specifications work bet
 * You cannot enable `mountPropagation` for volume mounts as this is not
   supported on Windows.
 
-#### Field compatibility for hostNetwork {#compatibility-v1-pod-spec-containers-hostnetwork}
+#### Host network access {#compatibility-v1-pod-sec-containers-hostnetwork}
 
-{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
+Kubernetes v1.26 to v1.32  included alpha support for running Windows Pods in the host's network namespace.
 
-The kubelet can now request that pods running on Windows nodes use the host's network namespace instead
-of creating a new pod network namespace. To enable this functionality pass `--feature-gates=WindowsHostNetwork=true` to the kubelet.
-
-{{< note >}}
-This functionality requires a container runtime that supports this functionality.
-{{< /note >}}
+Kubernetes v{{< skew currentVersion >}} does **not** include the `WindowsHostNetwork` feature gate
+or support for running Windows Pods in the host's network namespace.
 
 #### Field compatibility for Pod security context {#compatibility-v1-pod-spec-containers-securitycontext}