Create Ingress Controller in Private AKS - step by step

How to create and AKS ingress controller with private Azure Container Registry and Private AKS cluster.
Step-by-step guide:
github repo: github.com/oortizmcp/aks-ingr...
References:
Create Ingress Controller in AKS:
docs.microsoft.com/en-us/azur...
NGINX Ingress Controller:
docs.nginx.com/nginx-ingress-...
How to Contact:
LinkedIn: www.linkedin.com/in/omar-ortiz/
github: github.com/oortizmcp

[@lionheart2663]

The best part of this video is a) The setup process is top notch b) He clearly explain that the external IP of the ingress controller is coming from the aks subnet , something which current Microsoft article never explains. I would try this today in my lab and create a video in my upcoming tech channel on youtube.

[@manikandanm5567]

Awesome brother. Expecting more videos from you.

[@DadasoPawar-us3ir]

How to capture client IP in ngnix ingress controller? which custom header use for?

[@amjds1341]

Please also do some demo on ngnix letsencrypt setup on private LB

[@techwithimad4672]

🔥

[@angelospapadopoylos2818]

Can i change the ip of ngnix to be internal after the deploymnet?

[@namithcc]

hey Hello , Thank you for the video, Just one question. In Azure can we set up ssl cert for these privte cluster(Dev Env), for eg my set up (an ingress nginx ontroller, an internal load balancer) ?
Thanks

[@omarortiz5487]

Hi Namith, although I haven’t tested with SSL certificates, my understanding is that yes you can.
You can check the documentation here:
docs.Microsoft.com/en-us/azure/AKS/ingress-tls?tabs=azure-cli
You might need to use something like Let’s Encrypt to accomplish your goal.
You can also check this:
Https://www.patrickreidl.at/secure-azure-Kubernetes-with-lets-encrypt-certificates/
I hope it helps

[@prayashiupadhyay50]

Facing error: Service has no external IP assigned , showing pending.

[@bucky7466]

Facing below error while helm upgrade
Error: UPGRADE FAILED: pre-upgrade hooks failed: timed out waiting for the condition

[@omarortiz5487]

This could be the ingress controller version you are trying to deploy. I had the same issue and in order to make it work I had to be very specific on the ingress controller version and the helm version.
Check line 32 here where I downloaded the specific version 3.36.0 github.com/oortizmcp/aks-ingress-controller/blob/main/ingress/manual.sh
And see line 39 I specified the version of the helm github.com/oortizmcp/aks-ingress-controller/blob/main/ingress/configure-ingress-controller.sh