<p>I've done the installation of <code>Nginx Ingress Controller</code> by using this guide (<a href="https://kubernetes.github.io/ingress-nginx/deploy/" rel="nofollow noreferrer">https://kubernetes.github.io/ingress-nginx/deploy/</a>) in 2 steps: </p>

<pre><code>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/mandatory.yaml

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/cloud-generic.yaml
</code></pre>

<p>Then it created for me 2 entities :</p>

<p><a href="https://i.stack.imgur.com/rYaJl.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/rYaJl.jpg" alt="enter image description here"></a></p>

<p>first entity is called <code>ingress-nginx</code> in <code>service &amp; ingress</code> section and the second one:</p>

<p><a href="https://i.stack.imgur.com/JUvL9.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/JUvL9.png" alt="enter image description here"></a></p>

<p>inside workloads section called <code>nginx-ingress-controller</code>. Next step of my configuration process was creating service with Ingress type: </p>

<p><strong>ingress.yaml</strong></p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
 annotations:
  kubernetes.io/ingress.class: "nginx-ingress-controller"
  nginx.ingress.kubernetes.io/rewrite-target: /
  nginx.ingress.kubernetes.io/from-to-www-redirect: "true"
  kubernetes.io/ingress.global-static-ip-name: my static ip
 name: booknotes-ingress 
 namespace: 'default'  
spec:
 rules:
 - host: www.domain.com
   http:
     paths:
     - path: /*
       backend:
         serviceName: booknotes-service
         servicePort: 80
</code></pre>

<p>Then I've exposed <code>booknotes-service</code> from my <code>booknotes</code> (Depoloyment) with <code>Custer IP</code> type . But when I go to www.domain.com it is in a pending state . What I've done wrong ? And I don't really understand well all the flow from the request to my pod in this case. </p>

Andrey Radkevich
<p>Have you binded the external ip address of your ingress controller to your dns? Can you resolve the dns? Try <code>nslookup www.domain.com</code> and check if the ip address is the one of your ingress controller. </p>

<p>Once you resolve the problem with the dns you may get either a 404 or a 502 as response. Which means you are resolving but not passing traffic to the service. Update your question with that and we can continue. </p>

<p>Pd.- Remove the <code>/*</code> in the path definition of the ingress resource. Just <code>/</code></p>
