From 74319b604ce61674676c1ee4c502d0f9a03d75d2 Mon Sep 17 00:00:00 2001 From: Michael Michael Date: Sat, 23 Mar 2019 10:09:06 -0500 Subject: [PATCH] Update intro-windows-in-kubernetes.md (#13344) --- content/en/docs/setup/windows/intro-windows-in-kubernetes.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/docs/setup/windows/intro-windows-in-kubernetes.md b/content/en/docs/setup/windows/intro-windows-in-kubernetes.md index 4c255149bc76f..69d32e2f0c9be 100644 --- a/content/en/docs/setup/windows/intro-windows-in-kubernetes.md +++ b/content/en/docs/setup/windows/intro-windows-in-kubernetes.md @@ -237,6 +237,7 @@ The following networking functionality is not supported on Windows nodes * Overlay networking support in kube-proxy is an alpha release. In addition, it requires [KB4482887](https://support.microsoft.com/en-us/help/4482887/windows-10-update-kb4482887) to be installed on Windows Server 2019 * `kubectl port-forward` * Local Traffic Policy and DSR mode +* Windows containers connected to l2bridge, l2tunnel, or overlay networks do not support communicating over the IPv6 stack. There is outstanding Windows platform work required to enable these network drivers to consume IPv6 addresses and subsequent Kubernetes work in kubelet, kube-proxy, and CNI plugins. * Outbound communication using the ICMP protocol via the win-overlay, win-bridge, and Azure-CNI plugin. Specifically, the Windows data plane ([VFP](https://www.microsoft.com/en-us/research/project/azure-virtual-filtering-platform/)) doesn't support ICMP packet transpositions. This means: * ICMP packets directed to destinations within the same network (e.g. pod to pod communication via ping) work as expected and without any limitations * TCP/UDP packets work as expected and without any limitations