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

Running clustered solutions inside containers

MongoDB is a free and open source cross-platform, document-oriented database program that can run in cluster mode (using shards and ReplicaSets). In this example, we will run a three-node MongoDB ReplicaSet as that is much easier to configure than a full sharded cluster and is sufficient to demonstrate the principle of storing container state data persistently.

If you would like to learn more about MongoDB and advanced sharded cluster components, please refer to the official documentation: https://docs.mongodb.com/manual/core/sharded-cluster-components/.

Our MongoDB ReplicaSet architecture will look as follows:

The primary node is responsible for managing all write operations, and there can only be one primary in a ReplicaSet. The secondary nodes are only replicating the primary's oplog and apply the data operations so that their...