Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Kubernetes on Azure

You're reading from   Hands-On Kubernetes on Azure Automate management, scaling, and deployment of containerized applications

Arrow left icon
Product type Paperback
Published in May 2020
Publisher Packt
ISBN-13 9781800209671
Length 368 pages
Edition 2nd Edition
Tools
Arrow right icon
Authors (3):
Arrow left icon
Nills Franssens Nills Franssens
Author Profile Icon Nills Franssens
Nills Franssens
Gunther Lenz Gunther Lenz
Author Profile Icon Gunther Lenz
Gunther Lenz
Shivakumar Gopalakrishnan Shivakumar Gopalakrishnan
Author Profile Icon Shivakumar Gopalakrishnan
Shivakumar Gopalakrishnan
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface Section 1: The Basics
1. Introduction to Docker and Kubernetes FREE CHAPTER 2. Kubernetes on Azure (AKS) 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 and Azure AD 7. Monitoring the AKS cluster and the application Section 3: Leveraging advanced Azure PaaS services
8. Connecting an app to an Azure database 9. Connecting to Azure Event Hubs 10. Securing your AKS cluster 11. Serverless functions Index

Fixing storage mount issues

Earlier in this chapter, you noticed how the guestbook application lost data when the Redis master was moved to another node. This happened because that sample application didn't use any persistent storage. In this section, we'll cover an example of how PVCs can be used to prevent data loss when Kubernetes moves a Pod to another node. We will show you a common error that occurs when Kubernetes moves Pods with PVCs attached, and we will show you how to fix this.

For this, we will reuse the WordPress example from the previous chapter. Before we start, let's make sure that the cluster is in a clean state:

kubectl get all

This shows us just the one Kubernetes service, as shown in Figure 5.14:

Executing the kubectl get all command generates an output showing only one Kubernetes service running for now.
Figure 5.14: You should only have the Kubernetes service running for now

Let's also ensure that both nodes are running and Ready:

kubectl get nodes

This should show us both nodes in a Ready state, as shown...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image