Since Kubernetes GA has announced joining Windows nodes to a Linux-based cluster via the Windows Server version 1809, we only support Windows Server version 1809 and above in future.
This repo only packages docker.io/rancher/kubelet-pause, other related images info comes following:
- docker.io/rancher/hyperkube is operated by rancher/hyperkube, since v1.14.1.
- docker.io/rancher/flannel-cni is operated by rancher/flannel-cni, since v0.3.0.
Windows Server Core mode offers great advantages such as smaller hardware requirements, much smaller attack surface, and a reduction in the need for updates. Since it has no graphical user interface, Windows Server Core mode is best managed remotely.
Windows Server Core mode version is not an "update" or "service pack" for Windows Server 2016 and above. It's the current twice-yearly server release on the release track that is designed for customers who are moving at a “cloud cadence," such as those on rapid development cycles. This track is ideal for modern applications and innovation scenarios such as containers and micro-services. Each release in this track is supported for 18 months from the initial release.
For more about Semi-Annual Channel, plus tips for deciding which channel to join (or remain on) see Semi-Annual Channel Overview.
All images build from this repositry are based on Windows Server Core(Semi-Annual Channel) container image as below:
Currently, the Microsoft has released the following Core mode versions:
Older containers will run the same on newer hosts with Hyper-V isolation, and the same (older) kernel version will still be used. However, if you want to run a container based on a newer Windows build - it can only run on the newer host build. More detail about this, please check out here.
When you want to run some Hyper-V containers on Windows Server 2016 and above, please make sure which edition of your Windows host. An article from Thomas Krenn can help you.
- This image is released under the MIT License