Book Image

Hands-On Kubernetes on Windows

By : Piotr Tylenda
Book Image

Hands-On Kubernetes on Windows

By: Piotr Tylenda

Overview of this book

With the adoption of Windows containers in Kubernetes, you can now fully leverage the flexibility and robustness of the Kubernetes container orchestration system in the Windows ecosystem. This support will enable you to create new Windows applications and migrate existing ones to the cloud-native stack with the same ease as for Linux-oriented cloud applications. This practical guide takes you through the key concepts involved in packaging Windows-distributed applications into containers and orchestrating these using Kubernetes. You'll also understand the current limitations of Windows support in Kubernetes. As you advance, you'll gain hands-on experience deploying a fully functional hybrid Linux/Windows Kubernetes cluster for development, and explore production scenarios in on-premises and cloud environments, such as Microsoft Azure Kubernetes Service. By the end of this book, you'll be well-versed with containerization, microservices architecture, and the critical considerations for running Kubernetes in production environments successfully.
Table of Contents (23 chapters)
1
Section 1: Creating and Working with Containers
5
Section 2: Understanding Kubernetes Fundamentals
9
Section 3: Creating Windows Kubernetes Clusters
12
Section 4: Orchestrating Windows Containers Using Kubernetes

Installing the Kubernetes network

After the Kubernetes master has been initialized with kubeadm, the next step is the installation of the Pod network. We have covered Kubernetes networking options in Chapter 5, Kubernetes Networking, which explains in detail which Container Network Interface (CNI) plugins are supported for hybrid Windows/Linux clusters. For this on-premises cluster deployment, we will use the Flannel network with a host-gw backend (a win-bridge CNI plugin on Windows nodes). Remember that you can use this approach only if there is Layer 2 (L2) connectivity (no Layer 3 (L3) routing) between the nodes. In general, a host-gw backend is preferable as it is in a stable feature state, whereas an overlay backend is still in an alpha feature state for Windows nodes.

If you are interested in Flannel with overlay backend installation, please refer to the official documentation...