You're reading from Hands-on Kubernetes on Azure, Third Edition Use Azure Kubernetes Service to automate management, scaling, and deployment of containerized applications

Product type Paperback

Published in May 2021

Publisher Packt

ISBN-13 9781801079945

Length 528 pages

Edition 3rd Edition

Languages

JavaScript

Tools

Azure

Concepts

Containerization

Authors (3):

Gunther Lenz

Nills Franssens

Shivakumar Gopalakrishnan

View More author details

Table of Contents (22) Chapters

Preface

Hands-on Kubernetes on Azure – Third Edition

Foreword

Section 1: The Basics FREE CHAPTER

1. Introduction to containers and Kubernetes

2. Getting started with Azure Kubernetes Service

Section 2: Deploying on AKS

3. Application deployment on AKS

4. Building scalable applications

5. Handling common failures in AKS

6. Securing your application with HTTPS

7. Monitoring the AKS cluster and the application

Section 3: Securing your AKS cluster and workloads

8. Role-based access control in AKS

9. Azure Active Directory pod‑managed identities in AKS

10. Storing secrets in AKS

11. Network security in AKS

Section 4: Integrating with Azure managed services

12. Connecting an application to an Azure database

13. Azure Security Center for Kubernetes

14. Serverless functions

15. Continuous integration and continuous deployment for AKS

Index

CI/CD process for containers and Kubernetes

Before you start building a pipeline, it's good to understand the typical CI/CD process for containers and Kubernetes. In this section, the high-level process shown in Figure 15.1 will be explored in more depth. For a more detailed exploration on CI/CD and DevOps for Kubernetes, you are encouraged to explore the following free online eBook by Microsoft: https://docs.microsoft.com/dotnet/architecture/containerized-lifecycle/.

A representation of the container and Kubernetes CI/CD process

Figure 15.1: Container and Kubernetes CI/CD process

The process starts with somebody making code changes. Code changes could mean application code changes, changes to the Dockerfile used to build the container, or changes to the Kubernetes YAML files used to deploy the application on a cluster.

Once code changes are complete, those changes are committed to a source control system. Typically, this is a Git repository, but other systems, such as Subversion (SVN), also exist. In a Git...