Database Patterns with Azure Kubernetes Service Part 1: MySQL + Azure Managed Disk

My good friend Roy started another amazing series of post. Now it’s time for Database patterns with Azure Kubernetes

Roy Kim on Azure, Office 365 and SharePoint

One of the non-straight forward aspects of implementing for applications in Kubernetes is the stateful data store.

I will be showing 2 relational database patterns in Azure Kubernetes Service. Since containers are the fundamental building blocks, these are stateless by default. That is the containers can lose its data when it is terminated or fail. More design, setup and management effort are given to have stateful components in Kubernetes. And is very much the case for relational databases. I will show two stateful persistent database approaches for Azure Kubernetes.

  1. In-cluster database
    • MySQL containerized database in a Kubernetes pod
    • Persistent Storage provisioned as Azure Managed Disks
  2. Azure PaaS Database
    • External to the Kubernetes cluster
    • With managed Identity for
    • Networking via a private link

In-cluster database

I will show a containerized MySql database using the demo Deploying WordPress and MySQL with Persistent Volumes. This is representative of a standard web application…

View original post 654 more words

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.