<p>I have deployed Azure AKS using the below official terraform docs</p>
<p><a href="https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/kubernetes_cluster" rel="nofollow noreferrer">https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/kubernetes_cluster</a></p>
<p>I see bunch of resources created as well as Loadbalancer called <strong>Kubernetes</strong> automatically</p>
<p>After this I have deployed deployed the Run demo app with ingress as mentioned in docs below for hello world one &amp; two</p>
<p><a href="https://learn.microsoft.com/en-us/azure/aks/ingress-basic?tabs=azure-cli" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/azure/aks/ingress-basic?tabs=azure-cli</a></p>
<p>When I check the ingress resource I don't see any EXTERNAL IP address allocated &amp; the columns are blank.</p>
<p>I want to set up a sample end to end AKS cluster with load balancing &amp; a DNS record.</p>
<p><strong>Can some one let me know what am I doing wrong or is there any other repo with end to end examples?</strong></p>

John
<p>I usually recommend the following, which gives you control over the IP address etc.</p>
<ul>
<li>Deploy an Public IP address using Terraform (or ARM) alongside your AKS cluster</li>
<li>Give the AKS Kubelet identity &quot;Network Contributor&quot; permissions on that PIP</li>
<li>When deploying your Ingress, <a href="https://learn.microsoft.com/en-us/azure/aks/load-balancer-standard#specify-the-load-balancer-ip-address" rel="nofollow noreferrer">reference that existing PIP</a> (and its resource group). AKS will then use that IP for the deployed service.</li>
</ul>
<p>This way you can, for example, control whether the PIP is static or dynamic, if it's coming out of a given prefix range, etc.</p>
<p>Full example here: <a href="https://learn.microsoft.com/en-us/azure/aks/static-ip" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/azure/aks/static-ip</a></p>
