Understanding Ingress Controllers and Azure App Gateway for Azure Kubernetes Part 1: Intro

Roy Kim on Azure, Office 365 and SharePoint

I will share my experiences with a design and implementation of Azure Application Gateway for an Azure Kubernetes Service (AKS) cluster. This is so that you may get some practical insight as you plan and design for using the Azure App Gateway.

In this blog series, I will go over

  1. Fundamental Ingress concepts
  2. Architecture and deployment components
  3. My review, observations and insights

Typical Use Case: For an application that is required to be internet facing, it is recommended to have a networking appliance that allows for ingress traffic into your application where you can manage web security, networking and http/layer 7 traffic.

As a result, a valuable option is to leverage the Azure Application Gateway as part of your overall Azure Kubernetes system architecture.

AKS Architecture

My implementation was based on the following documentation. So read the following article to further understand background details.

The fundamentals of an Ingress and an…

View original post 430 more words

One thought on “Understanding Ingress Controllers and Azure App Gateway for Azure Kubernetes Part 1: Intro

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.