<p>I was trying to understand the relation between <code>Kubernetes</code> <code>Ingress Resource</code> and <code>Ingress Controller</code>.
I read that <code>Ingress</code> resource is mainly the rules and controller Pods route the traffic actually for Ingress rules.</p>
<p>I'm confused, like other Objects why <code>Ingress</code> resource can not spin up PODs on its own by specifying the image.</p>
<p>Secondly, how <code>Ingress Object</code> connects to actual <code>Ingress Controller Pods</code> to get its work done ( or say other way round). I don't see specifying any selector in the <code>Ingress Object</code>.</p>
<p>Thirdly, if the <code>Ingress Resource</code> gets its own IP address ( internal or external) then why <code>Ingress Controller</code> needs external IP address.</p>
<p>thanks</p>
<p>PS: I do not have a great knowledge of Kubernetes, please pardon if the questions sound silly.</p>

Learner
<p>Details with diagram are posted in GKE tutorial
<a href="https://cloud.google.com/community/tutorials/nginx-ingress-gke" rel="nofollow noreferrer">Ingress with NGINX controller on Google Kubernetes Engine
</a></p>
