-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.
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
Windows: List of APIs/features disabled or with degraded functionality on Windows #13322
Comments
cc @envoyproxy/windows-dev |
@mattklein123 do you think this is appropriate for the help wanted tag? |
Sure! |
This is part of the #13190 roll-up issue |
Note specifically issue 13596 for CA path spec differences between windows and linux |
Note specifically issue 13964 for differences between /dev/null vs. NUL, missing /dev/ devices stdout, stderr, tty, console |
Commit Message: Adds note in the docs for features that are not supported on Windows See #13322 Risk Level: N/A Testing: N/A Docs Changes: Only docs Release Notes: N/A Signed-off-by: Sotiris Nanopoulos <[email protected]>
@sunjayBhatia was #15298 sufficient? |
Yeah I think we could close this since we have documentation for the various things that are disabled and have plans to have some automated generation around those docs |
Closing based on the discussion in the windows-dev group and the comment above. |
To set expectations about Windows support through the release phases (Alpha evaluation, GA, etc.), we should document the currently disabled or degraded features on Windows
For now this list includes (non-exhaustive):
Signal handling/process lifecycle control is disabledPer-request RTT latency metrics Per-request rtt latency metrics in HTTP filters #12305Please add comments for additional APIs/features that should be mentioned and we will get them added to the list.
This could instead be a document in the Envoy source tree, or a GitHub issue tag instead to allow us easier iteration/addition if the maintainers think it is more appropriate.
The text was updated successfully, but these errors were encountered: