Book Image

Hands-On Kubernetes on Azure

By : Shivakumar Gopalakrishnan, Gunther Lenz
Book Image

Hands-On Kubernetes on Azure

By: Shivakumar Gopalakrishnan, Gunther Lenz

Overview of this book

Microsoft is now one of the most significant contributors to Kubernetes open source projects. Kubernetes helps to create, configure, and manage a cluster of virtual machines that are preconfigured to run containerized applications. This book will be your guide to performing successful container orchestration and deployment of Kubernetes clusters on Azure. You will get started by learning how to deploy and manage highly scalable applications, along with understanding how to set up a production-ready Kubernetes cluster on Azure. As you advance, you will learn how to reduce the complexity and operational overheads of managing a Kubernetes cluster on Azure. By the end of this book, you will not only be capable of deploying and managing Kubernetes clusters on Azure with ease, but also have the knowledge of best practices for working with advanced AKS concepts for complex systems.
Table of Contents (16 chapters)
Free Chapter
1
Section 1: The Basics
4
Section 2: Deploying on AKS
10
Section 3: Leveraging Advanced Azure PaaS Services in Combination with AKS

Deploying the sample guestbook application

In this chapter, we will deploy the classic guestbook sample Kubernetes application. We will be mostly following the steps from https://Kubernetes.io/docs/tutorials/stateless-application/guestbook/ with some modifications. We employ these modifications to do the following:

  • Make the solution more AKS friendly
  • Show additional concepts, such as ConfigMaps, that are not present in the original sample

As mentioned in the Kubernetes documentation, you will be deploying a simple, multi-tier web application. You know it is a good sign for a platform when the documentation says it is a simple application that has master/slave backends and a scalable fronted. The guest book solution is also categorized as a stateless application because the frontend doesn't store any state. It is stateful for the single instance of Redis master, which stores...