<p>I used this article as reference to install my ingress on azure's cloud. <a href="https://learn.microsoft.com/pt-br/azure/aks/ingress-tls" rel="nofollow noreferrer">https://learn.microsoft.com/pt-br/azure/aks/ingress-tls</a></p>

<p>But now I have some questions about it, how to manage that,like:
On this step I installed my nginx-ingress:</p>

<p><code>helm install stable/nginx-ingress \
    --namespace ingress-basic \
    --set controller.replicaCount=2 \
    --set controller.nodeSelector."beta\.kubernetes\.io/os"=linux \
    --set defaultBackend.nodeSelector."beta\.kubernetes\.io/os"=linux \
    --set name=MY_RELEASE_NAME
</code>
After that I had a LoadBalancer and a ClusterIP created and I must update manually my FQDN with the Public IP provided(azure provides)! e.g: 
<code>az network public-ip update --ids $PUBLICIPID --dns-name $DNSNAME</code></p>

<p>Is there any risk of this controller be destroyed and I lose my public IP and then have to create everything manually again? 
If the answer is YES, how to do? Create a new job on azure to update it automatically? Does anyone know a sample of that?</p>

Paulo Sérgio Vieira
<p>Follow the below steps</p>

<ol>
<li>Create a public ip to be used as LoadBalancer Ip address using azure CLI. choose it as static ip</li>
<li>Create nginx YAML template using helm template command ( replace install with template in your command )</li>
<li>Update the nginx service type as LoadBalancer and update the LoadBalancer ip from step 1 in the template generated in step2 above</li>
<li>Deploy the helm template YAML</li>
</ol>
