Comparing Azure Kubernetes Networking Scenarios – Part 4 Http App Routing

Roy Kim on Azure and Microsoft 365

In this 3rd configuration profile, I will walk through the resulting configuration of AKS and its effect on the Load Balancer, Virtual Network, VM network interface card, deploy and test a web application into the Azure Kubernetes Service (AKS) cluster. The configuration profile is mainly around the Azure CNI network model and enabling the HTTP Application Routing Feature.
The HTTP application routing solution makes it easy to access applications that are deployed to your Azure Kubernetes Service (AKS) cluster. When the solutionโ€™s enabled, it configures anIngress controllerin your AKS cluster. As applications are deployed, the solution also creates publicly accessible DNS names for application endpoints.

Please read the Part 1 intro of this blog series if you havenโ€™t already. This will explain the background and what each configuration setting means. Here is the previous blog post for Part 3 Azure CNI.

Configuration Profile 3

  • Network Model/Type: Advancedโ€ฆ

View original post 289 more words

Leave a comment

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

You are commenting using your 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.

%d bloggers like this: