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

Summary

This chapter introduced you to multiple network security options in AKS. You explored both securing the control plane and the workload in the cluster.

To secure the control plane, you first used authorized IP ranges to verify that only allowed public IP addresses can access the control plane of your cluster. After that, you created a new private cluster, which was only reachable using a private connection. You connected to that private cluster using Azure Private Link.

After that, you also explored workload network security. Initially, you deployed a public service, which was available for all users. You then had AKS configure Azure NSGs to secure that service only to an allowed connection. You verified that you could connect to the service from your machine, but not from a VM in Azure, as expected. Finally, you also configured Kubernetes network policies in a new cluster. You used those to protect pod-to-pod traffic and were able to secure traffic between different pods...