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