Skip to content
This repository was archived by the owner on Jan 11, 2023. It is now read-only.

Update window binary build documentation #2147

Merged
merged 2 commits into from
Jan 25, 2018
Merged

Update window binary build documentation #2147

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ea6ea32
Update window binary build documentation
JiangtianLi Jan 24, 2018
00c4cfb
move background section
JiangtianLi Jan 24, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/kubernetes-build-win-binaries.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,18 +4,18 @@ The following instructions show how to deploy the Windows Kubernetes Binaries an

### Prerequisites
* Azure Storage Account and Azure Storage Container to store Windows binaries
* Access to [winnat.sys](https://blogs.technet.microsoft.com/virtualization/2016/05/25/windows-nat-winnat-capabilities-and-limitations/) stored in a storage container. (WinNAT) is used to provide required NAT networking functionality for Windows containers that will be included in a future Windows image update.
* Access to [wincni.exe] (https://github.com/Microsoft/SDN/tree/master/Kubernetes/windows/cni) stored in a storage container. Windows CNI is a plugin that supports the Container Network Interface (CNI) network model and interfaces with the Windows Host Networking Service (HNS) to configure host networking and policy.
* Docker installed and running. MacOS users using Docker for Mac must have at [least 3GB of memory allocated to Docker](https://github.com/kubernetes/kubernetes/tree/master/build/#requirements) or building will likely fail.

## Background
Microsoft maintains a fork of the Kubernetes project at https://github.com/Azure/kubernetes which includes patches not yet included in upstream Kubernetes; these are needed for Windows containers to function.
Microsoft maintains a fork of the Kubernetes project at https://github.com/Azure/kubernetes which includes patches not yet included in upstream Kubernetes for release 1.7 and 1.8; these are needed for Windows containers to function. *From release 1.9, all Windows features are in upstream and Windows binaries no longer needs to be built from Azure fork.*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great. Can we move the background to the top as to make it front and center? Ideally most folks will see that from v1.9+ there's no need to do anything special for Windows nodes and hackers can continue reading if they want to build their own.


[build-windows-k8s.sh](../scripts/build-windows-k8s.sh) does the following:
- Checks out the fork of Azure/kubernetes (includes Windows fixes not yet in upstream Kubernetes, needed for Windows containers to function)
- Builds kubelet.exe and kube-proxy.exe from source in a Docker container
- Downloads kubectl.exe for desired release
- Downloads [NSSM](https://nssm.cc) which is used to start kubelet and kube-proxy on Windows
- Downloads [Windows NAT](https://blogs.technet.microsoft.com/virtualization/2016/05/25/windows-nat-winnat-capabilities-and-limitations/)
- Downloads [Windows CNI](https://github.com/Microsoft/SDN/tree/master/Kubernetes/windows/cni)
- Creates an .zip archive of these Windows components
- Uploads archive to Azure Blob Storage

Expand Down