Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
122 lines (82 sloc) 9.47 KB

Contributing on Windows Node support

Contains a list of common resources when contributing in the effort to support Windows Node and Windows Server containers in Kubernetes.

Joining the community of other contributors

The best way to get in contact with the contributors working on Windows support is through the Kubernetes Slack. To get a Slack invite, visit . Once you're logged in, join us in the #SIG-Windows channel. You can also use the Kubernetes Community Forums to chat about Windows containers on Kubernetes.

To get access to shared documents, meeting calendar, and additional discussions, be sure to also join the SIG-Windows Google Group.

View the leadership team in SIG-Windows and other subprojects in the getting started guide.

Find work in progress

To get a handle on current work, you can view outstanding PRs.

View the SIG-Windows project board, tracking detailed issues across Kubernetes releases.

Building Kubernetes for Windows from Source

The Kubernetes build scripts have not been ported to Windows, so it's best to run in a Linux VM where you can run the same Docker container used in the official Kubernetes builds. This simplifies the steps, but means that you cannot build under Windows Subsystem for Linux (WSL).

It's best to skim over the Building Kubernetes guide if you have never built Kubernetes before to get the latest info. These steps are a summary focused on cross-building the Windows node binaries (kubelet & kube-proxy).

Build Prerequisites

At least 60GB of disk space is required, and 16GB of memory (or memory + swap).

Once you have a VM, install Git, Docker-CE, and make. The build scripts will pull a Docker container with the required version of golang and other needed tools preinstalled.

If you're using Ubuntu, then install the following packages: git, build-essential, Docker-CE.

Building Kubernetes binaries for Windows

You can build individual components such as kubelet, kube-proxy, or kubectl by running ./build/ make <binary name> KUBE_BUILD_PLATFORMS=windows/amd64 such as ./build/ make kubelet KUBE_BUILD_PLATFORMS=windows/amd64

If you would like to build all binaries at once, then run ./build/ make cross KUBE_BUILD_PLATFORMS=windows/amd64

Once the build completes, the files will be in _output/dockerized/bin.

Updating the Node binaries

Once you have binaries built, the easiest way to test them is to replace them on an existing cluster. This section assumes you already have a cluster in the cloud of your choice. To update the binaries on an existing node, follow these steps:

  1. Drain & cordon a node with kubectl drain <nodename>
  2. Connect to the node with SSH or Windows Remote Desktop, and start PowerShell
  3. On the node, run Stop-Service kubelet -Force
  4. Copy kubelet.exe and kube-proxy.exe to a cloud storage account, or use SSH to copy them directly to the node.
  5. Overwrite the existing kubelet & kube-proxy binaries. If you don't know where they are, run sc.exe qc kubelet or sc.exe qc kube-proxy and look at the BINARY_PATH_NAME returned.
  6. Start the updated kubelet & kube-proxy with Start-Service kubelet

Creating a PR

Congratulations on contributing to the SIG-Windows ecosystem. If there is a PR you would like to build, it's easy. You can create a working branch, pull the changes from GitHub in a patch, apply, then build.

The detailed steps here are based off an example PR on GitHub: Be sure to replace the URL and steps with the PR you want to test.

  1. Make sure your local clone is up-to-date with master: git checkout master ; git pull master
  2. Create a branch in your repo: git checkout -b pr74788
  3. Get the patch for the PR you want. Append .patch to the URL, and download it with curl: curl -L -o pr74788.patch
  4. Merge it with patch -p1 < pr74788.patch
  5. If there are errors, fix them as needed. Once you're done, delete the .patch file and then git commit the rest to your local branch.
  6. Deploy your own cluster, including Windows Nodes
  7. Test Your Changes

API Considerations

If you modifying an API in the SIG-Windows codebase, make sure you are aware of the API guidelines and conventions used in Kubernetes. This document offers guidelines for API reviewers that API developers should always have in consideration.

Running Tests

For the most up-to-date steps on how to build and run tests, please go to It has everything you need to build and run tests, as well as links to the SIG-Windows configurations used on TestGrid.

Reporting Issues and Feature Requests

If you have what looks like a bug, or you would like to make a feature request, please use the Github issue tracking system. You can open issues on GitHub and assign them to SIG-Windows. You should first search the list of issues in case it was reported previously and comment with your experience on the issue and add additional logs. SIG-Windows Slack is also a great avenue to get some initial support and troubleshooting ideas prior to creating a ticket.

If filing a bug, please include detailed information about how to reproduce the problem, such as:

  • Kubernetes version: kubectl version
  • Environment details: Cloud provider, OS distro, networking choice and configuration, and Docker version
  • Detailed steps to reproduce the problem
  • Relevant logs
  • Tag the issue sig/windows by commenting on the issue with /sig windows to bring it to a SIG-Windows member's attention

Gathering Logs

Logs are an important element of troubleshooting issues in Kubernetes. Make sure to include them any time you seek troubleshooting assistance from other contributors.

Collecting kubelet and kube-proxy Logs

There are a few different ways to run the node binaries (kubelet, kube-proxy, etc) and the execution method also dictates how logs will be collected. Issue 75319 tracks pending work for better log management on Windows (for example using the Windows Event Log for higher log throughput and log rotation). If you end up logging to a file, you can use fluentd or Splunk to ship logs to a syslog server for search and analytics.

  1. Windows Service Manager services - You may have to introduce your own log consumption and log rotation service if you are logging to a file. We will investigate if journald is an option
  2. nssm.exe services - nssm.exe provides support for forwarding stdout/stderr logs to a file (use the AppStdout and AppStderr options) and also supports logs file rotation (See the File rotation and I/O redirection sections in the documentation). You can see more examples on using nssm.exe for the Kubernetes components of the Windows node in the services and background processes section under troubleshooting
# Example nssm command line for the kubelet
nssm set kubelet AppStdout C:\k\kubelet.log
nssm set kubelet AppStderr C:\k\kubelet.log

Collecting Networking Logs

  1. On the node before creating the pod for the first time.
  2. start-bitstransfer
  3. Execute collectlogs.ps1 in a PowerShell window 4 Start the trace by running C:\k\debug\starthnstrace.cmd
  4. Reproduce the issue
  5. Run netsh trace stop
  6. Execute collectlogs.ps1 in a PowerShell window again
  7. Include in your ticket C:\server.etl
You can’t perform that action at this time.