Hello @Jacques Patricks ,
I believe you have deployed Nginx Ingress Controller using Helm package to expose your application.
I am not sure what problem you were experiencing but Nginx ingress controller implementation should be a straight forward.
Have a look at the basic ingress controller implementation here https://learn.microsoft.com/en-us/azure/aks/ingress-basic with the sample test application.
When you are using NGINX ingress controller please double check below things:
1) Ingress Controller (double check annotations)
"If you have multiple node pools (Windows + Linux) , please make sure the nginx controller pod installed in Linux pool."
2) Ingress rules
3) URL or Path based routing.
(Above basic document should help you out in understanding)
(Please note the order above i.e. Ingress Controller should be deployed first before Ingress rules)
If you want to configure custom ingress controller to use Https:- please see https://learn.microsoft.com/en-us/azure/dev-spaces/how-to/ingress-https-nginx#configure-a-custom-nginx-ingress-controller
FYI ,
We have other ingress controllers like Application Gateway Ingress Controller which can be deployed/configured using Helm or Aks add-on
What is Application Gateway Ingress Controller?
https://learn.microsoft.com/en-us/azure/application-gateway/ingress-controller-overview#:~:text=AGIC%20monitors%20the%20Kubernetes%20cluster,of%20Kubernetes%20Resources%20for%20changes.
Enable Application Gateway Ingress Controller add-on for an existing AKS cluster with an existing Application Gateway through Azure CLI (Preview)
https://learn.microsoft.com/en-us/azure/application-gateway/tutorial-ingress-controller-add-on-existing
Hope above points help you out in resolving the issue , kindly let me know if you have additional questions.
If this helps , make sure to "Accept Answer" so that it will help the community out there.