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

Choosing Kubernetes network modes

Network modes (drivers) is a concept from Docker that is a part of the Container Network Model (CNM). This specification was proposed by Docker to solve container networking setup and management challenges in a modular, pluginable way. Docker's libnetwork is the canonical implementation of the CNM specification.

At this point, you are probably wondering how CNM relates to CNI, which solves a similar problem. Yes, they are competing specifications for container networking! For Linux containers, the implementations of Docker network drivers and CNI can be considerably different. However, for Windows containers, network drivers implemented in libnetwork are a simple shim for HNS that performs all the configuration tasks. CNI plugins, such as win-bridge and win-Overlay, do exactly the same thing: call the HNS API. This means that for Windows...