Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added Windows KEP clarification on ICMP protocol support. #824

Merged
merged 3 commits into from Feb 27, 2019
Merged

Added Windows KEP clarification on ICMP protocol support. #824

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a9c18d9
Added Windows KEP clarification on ICMP protocol support.
daschott Feb 12, 2019
b7364a3
Fixed typos
daschott Feb 12, 2019
a554c56
added note on ability to substitute ping with curl on Windows
daschott Feb 26, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 6 additions & 1 deletion keps/sig-windows/20190103-windows-node-support.md
View file
Open in desktop
Expand Up @@ -5,6 +5,7 @@ authors:
- "@benmoss"
- "@patricklang"
- "@michmike"
- "@daschott"
owning-sig: sig-windows
participating-sigs:
- sig-architecture
Expand All @@ -21,7 +22,7 @@ approvers:
- "@spiffxp"
editor: TBD
creation-date: 2018-11-29
last-updated: 2019-01-29
last-updated: 2019-02-11
status: implementable
---

Expand Down Expand Up @@ -153,6 +154,10 @@ Note that some features are plain unsupported while some will not work without u
- Not all features of shared namespaces are supported. This is clarified in the API section below
- The existing node problem detector is Linux-only and requires privileged containers. In general, we don't expect these to be used on Windows because there's no privileged support
- Overlay networking support in Windows Server 1803 is not fully functional using the `win-overlay` CNI plugin. Specifically service IPs do not work on Windows nodes. This is currently specific to `win-overlay`; other CNI plugins (OVS, AzureCNI) work. Since Windows Server 1803 is not supported for GA, this is mostly not applicable. We left it here since it impacts beta
- Outbound communication using the ICMP protocol via the `win-overlay`, `win-bridge`, and `Azure-CNI` plugin. Specifically, the Windows datapath (VFP) doesn't support ICMP packet transpositions. This means:
daschott marked this conversation as resolved.
Show resolved Hide resolved
- ICMP packets directed to addressses within the same network (e.g. pod to pod communication via ping) will work as expected and without any limitations
daschott marked this conversation as resolved.
Show resolved Hide resolved
- TCP/UDP packets will work as expected and without limitations
- ICMP packets directed to pass through a remote network (e.g. pod to external internet communication via ping) cannot be transposed and thus will *not* be routed back to their source

### Windows Container Compatibility
As noted above, there are compatibility issues enforced by Microsoft where the host OS version must match the container base image OS. Changes to this compatibility policy must come from Microsoft. For GA, since we will only support Windows Server 2019 (aka 1809), both `container host OS` and `container OS` must be running the same version of Windows, 1809.
Expand Down