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

Deploying Azure Database for MySQL using ASO

In the previous section, you deployed ASO on your Kubernetes cluster. This means that now you can use the Kubernetes API to deploy Azure resources. In this section, you will create a MySQL database running on the Azure Database for MySQL service using YAML files that you will submit to Kubernetes using kubectl. Let's get started:

First, you need to create a resource group. The code for the resource group definition is also available in the code samples with this chapter. Create this file and save it as rg.yaml:
```
apiVersion: azure.microsoft.com/v1alpha1
kind: ResourceGroup
metadata:
  name: aso-resources
spec:
  location: <cluster location>
```
As you can see in the code for the resource, apiVersion refers to azure.microsoft.com and kind is ResourceGroup. Furthermore, you provide the details for the resource group, being its name and its location. Make sure to change location to the location of your cluster...