Skip to content

How to create an Azure Kubernetes Service (AKS) with Application Gateway as ingress controller - Fully Automated

Notifications You must be signed in to change notification settings

gustavozimm/terraform-aks-app-gateway-ingress

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

How to create an Azure Kubernetes Service (AKS) with Application Gateway as ingress controller

Introduction

After read the article on how to Create an Application Gateway ingress controller in Azure Kubernetes Service, it is clear the solution is not fully automated. The solution presented created all the components, like AKS Cluster, Application Gateway, and Virtual Network, but does not perform the ingress controller configuration, meaning, do not set up AAD Pod Identity, Service Principal, etc. One of my customers challenged me to have everything automated, so here we go. The objective of this article is to present a fully automated deployment of Azure Kubernetes Services using Application Gateway as Ingress Controller.

Workloads Deployed

The Terraform template is configured to deploy the following components:

  • Azure Kubernetes Services
  • Azure Application Gateway
  • Azure Database for MySQL
  • Virtual Network with two subnets
    • Subnet for AKS nodes
    • Subnet for Application Gateway
  • Public IP
  • Persistent Volume Claim (PVC)

Prerequisites

Setup correct subscription

Terraform Variables Config files

Declaring Variables

Defining Resources

About

How to create an Azure Kubernetes Service (AKS) with Application Gateway as ingress controller - Fully Automated

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages