AKS 1.22.*, 1.23.* Ingress-Nginx Not Working.

[peter-miroshnikov]

What happened:
Cluster Unreachable using Ingress-nginx.
Fresh AKS with kubernates version 1.22.* and 1.23.*
Helm install ingress-nginx v 4.. ( tried 4.0.* and 4.1.0 )
All Azure resources are created. (LoadBalancer, Rules, IP's) nut no traffic reaches the cluster
The traffic never reaches the cluster.

What you expected to happen:
In kubernetes 1.21.* with Ingress-nginx helm chart v. 3.41.0 i have no issues reaching the cluster by any means.
In kubernates 1.22 + (1.22.* and 1.23.*) i cant reach my cluster at all using Ingress-nginx

How to reproduce it (as minimally and precisely as possible):
Powerup new AKS v 1.22.* using Azure network plugin

Install the Ingress
helm upgrade --install ingress-nginx ingress-nginx
--repo https://kubernetes.github.io/ingress-nginx
--namespace ingress-nginx --create-namespace

Find the IP of the loadbalancer.
kubectl config set-context --current --namespace=ingress-nginx
kubectl get svc

It is the external IP of the ingress service.

Try reaching the IP.
It never reaches the ingress pods.
No logs, no traffic.
No Errors.

[ghost]

Hi peter-miroshnikov, AKS bot here 👋
Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.

I might be just a bot, but I'm told my suggestions are normally quite good, as such:

1. If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
2. Please abide by the AKS repo Guidelines and Code of Conduct.
3. If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
4. Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
5. Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue.
6. If you have a question, do take a look at our AKS FAQ. We place the most common ones there!

[aristosvo]

It seems the same or similar as this solved issue on the kubernetes/ingress-nginx repo itself.

Use the flag --set controller.service.externalTrafficPolicy=Local should probably fix it.

This seems also a duplicate of #2903.

[peter-miroshnikov]

I can confirm, this fixed my issue.
I am sorry for the duplications.