Adding a warning to Windows docs for NodePort service issues on WS2022 (#31759)
* Adding a warning to Windows docs for NodePort service issues on WS2022 Signed-off-by: Mark Rossetti <marosset@microsoft.com> * Update content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md Co-authored-by: Jihoon Seo <46767780+jihoon-seo@users.noreply.github.com> * Update content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md Co-authored-by: Tim Bannister <tim@scalefactory.com> Co-authored-by: Jihoon Seo <46767780+jihoon-seo@users.noreply.github.com> Co-authored-by: Tim Bannister <tim@scalefactory.com>pull/31816/head
parent
9da7dead81
commit
1b1dd7d9ae
|
@ -327,6 +327,17 @@ In a cluster that includes Windows nodes, you can use the following types of Ser
|
|||
* `LoadBalancer`
|
||||
* `ExternalName`
|
||||
|
||||
{{< warning >}}
|
||||
There are known issue with NodePort services on overlay networking, if the target destination node is running Windows Server 2022.
|
||||
To avoid the issue entirely, you can configure the service with `externalTrafficPolicy: Local`.
|
||||
|
||||
There are known issues with pod to pod connectivity on l2bridge network on Windows Server 2022 with KB5005619 or higher installed.
|
||||
To workaround the issue and restore pod-pod connectivity, you can disable the WinDSR feature in kube-proxy.
|
||||
|
||||
These issues require OS fixes.
|
||||
Please follow https://github.com/microsoft/Windows-Containers/issues/204 for updates.
|
||||
{{< /warning >}}
|
||||
|
||||
Windows container networking differs in some important ways from Linux networking.
|
||||
The [Microsoft documentation for Windows Container Networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture) provides
|
||||
additional details and background.
|
||||
|
|
Loading…
Reference in New Issue