<p>I am deploying our system onto AKS, using kubectl. 
I have the following deployed:</p>

<p>Namespace: kube-system
- Kubernetes NGINX controller 
- Default back end</p>

<p>Namespace: default
- 3 ingress objects, each consisting of multiple rules. Each is bound to a different sub domain. When I ping the sub domains the correct IP is set (i.e. the ingress controller)
- The services which are to be accessed are also deployed in this namespace.</p>

<p>The ingress controller has created successfully, received and EIP etc and when I go to this IP I get the default back end. So far so good.</p>

<p>However, I then start to add the Ingress objects - all looks good in the ingress controller logs, adding the rules and reloading the back end with all appropriate rules however when i then try to access any of the new URLs, i.e. 
<a href="http://ingress1.ourdomain.com/ingressrule1" rel="nofollow noreferrer">http://ingress1.ourdomain.com/ingressrule1</a> the request just times out.</p>

<p>I have set the level of debugging up to v3 on the ingress controller and all looks as expected in the logs. The only thing I can think of is that the controller and ingress &amp; associated services are in different namespaces? But this seems to be the correct way to set this up. I have trawled many web pages now, and although the docs at: <a href="https://kubernetes.github.io/ingress-nginx/how-it-works/" rel="nofollow noreferrer">https://kubernetes.github.io/ingress-nginx/how-it-works/</a> and <a href="https://kubernetes.github.io/ingress-nginx/troubleshooting/" rel="nofollow noreferrer">https://kubernetes.github.io/ingress-nginx/troubleshooting/</a> are helpful they haven't provided and clues for my situation.</p>

<p>Has anyone come across anything similar at all?</p>

Robert Young
<p>Timeout issues are usually related to network (security groups) problems</p>

<p>Can you make sure the port 80 is open on the security group of the instance that has the EIP your are pointing to ?</p>
