Home • Explore • Blog • CI
☰



kubernetes
2nd chunk of `content/en/blog/_posts/2016-12-00-Windows-Server-Support-Kubernetes.md`
0aac3ebf818ff6c6e2b6f4da7a7809d47f597707f72045fb0000000100000b10
The process to bring Windows Server to Kubernetes has been a truly multi-vendor effort and championed by the [Windows Special Interest Group (SIG)](https://github.com/kubernetes/community/blob/master/sig-windows/README.md) - Apprenda, Google, Red Hat and Microsoft were all involved in bringing Kubernetes to Windows Server. On the community effort to bring Kubernetes to Windows Server, Taylor Brown, Principal Program Manager at Microsoft stated that “This new Kubernetes community work furthers Windows Server container support options for popular orchestrators, reinforcing Microsoft’s commitment to choice and flexibility for both Windows and Linux ecosystems.”  

**Guidance for Current Usage**  


|
Where to use Windows Server support?
 |
Right now organizations should start testing Kubernetes on Windows Server and provide feedback. Most organizations take months to set up hardened production environments and general availability should be available in next few releases of Kubernetes.
 |
|
What works?
 |
Most of the Kubernetes constructs, such as Pods, Services, Labels, etc. work with Windows Containers.
 |
|
What doesn’t work yet?
 |

- Pod abstraction is not same due to networking namespaces. Net result is that Windows containers in a single POD cannot communicate over localhost. Linux containers can share networking stack by placing them in the same network namespace.
- DNS capabilities are not fully implemented
- UDP is not supported inside a container

 |
|
When will it be ready for all production workloads (general availability)?
 |
The goal is to refine the networking and other areas that need work to get Kubernetes users a production version of Windows Server 2016 - including with Windows Nano Server and Windows Server Core installation options - support in the next couple releases.
 |


**Technical Demo**  




**Roadmap**  

Support for Windows Server-based containers is in alpha release mode for Kubernetes 1.5, but the community is not stopping there. Customers want enterprise hardened container scheduling and management for their entire tech portfolio. That has to include full parity of features among Linux and Windows Server in production. The [Windows Server SIG](https://github.com/kubernetes/community/blob/master/sig-windows/README.md) will deliver that parity within the next one or two releases of Kubernetes through a few key areas of investment:  

- **Networking** - the SIG will continue working side by side with Microsoft to enhance the networking backbone of Windows Server Containers, specifically around lighting up container mode networking and native network overlay support for container endpoints. 
- **OOBE** - Improving the setup, deployment, and diagnostics for a Windows Server node, including the ability to deploy to any cloud (Azure, AWS, GCP)
Title: Collaboration, Guidance, and Roadmap for Windows Server Support in Kubernetes
Summary
The addition of Windows Server support in Kubernetes was a collaborative effort led by the Windows SIG, including Apprenda, Google, Red Hat, and Microsoft. Organizations are encouraged to test and provide feedback, with general availability expected in future releases. Core Kubernetes constructs work with Windows Containers, but limitations exist around pod networking, DNS, and UDP support. The roadmap focuses on enhancing networking capabilities and improving the out-of-box experience for Windows Server nodes, with the goal of achieving feature parity between Linux and Windows Server within the next one or two Kubernetes releases.