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

Preface

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

Readiness and liveness probes

Readiness and liveness probes were briefly touched upon in the previous section. In this section, you'll explore them in more depth.

Kubernetes uses liveness and readiness probes to monitor the availability of your applications. Each probe serves a different purpose:

A liveness probe monitors the availability of an application while it is running. If a liveness probe fails, Kubernetes will restart your pod. This could be useful to catch deadlocks, infinite loops, or just a "stuck" application.
A readiness probe monitors when your application becomes available. If a readiness probe fails, Kubernetes will not send any traffic to the unready pods. This is useful if your application has to go through some configuration before it becomes available, or if your application has become overloaded but is recovering from the additional load. By having a readiness probe fail, your application will temporarily not get any more traffic...