Hi Paulo. This is a Ingress Controller, that controls how Ingress works and provides additional resources to use within your ingressses like "Annotations". The one that you mention is built on top of nginx. The Ingress Controller is deployed as a DaemonSet and looks on the apiserver's "/ingresses" endpoint for existing ingress definitions. WIth this information the Ingress Controller can use the cloud API to provide the IP from the Cloud Load Balancer used in the ingress, permiting external access. The ingress itself is just a definition that connects the external world outside the cluster to the services/pods inside it, but additional logic is required to make your cloud to see what's visible. The Ingress Controller is responsible for doing the other things to make this internal world accessible over the ingress. Using GKE or AKS kubernetes clusters the Ingress Controller is created automatically, so when you create a new ingress, the ingress Controller watch this creation and quickly create the necessary configurations in your cloud to viabilize the external access. In Bare-metal deployments, you must deploy the Ingress Controller for the ingress resource to work correctly.
After 2 years and it is still very helpful, thank you
This video resolved all my queries related to Ingress controller. Thanks you vey much for the excellent video
I understand ingress more now over lunch than I did an hour ago. Thanks for the videos!
Your webinar is so good, I was struggling to understand Kubernetes networking on GKE and this made it all clear. Thanks a lot!
This should be the default introductory video to k8s Ingress. Pretty clear demo!
It was a great Webinar very easy to understand and made lot of sense, thank you Sir for sharing the content
One year later and still very informative. Thanks for this
Thanks most awaited videos in kubernetes series.
Excellent ingress intro and demo. It is really useful.
Fantastic presentation. Great overview of Ingress.
Very well explained. Thank you for creating this series.
great webinar ..got good clarity on the concepts
That was a great experience watching and going through your webinar. Congrats for your work.
this is gold!! thank you Janakiram!
Thank you! This was exactly what I was looking for. Nice job.
Awesome introduction. thank you very much!
Beautifully well explained!
GREAT explanations sir, thank you!
Excellent tutorial! Thank you very much!
very nice sir
Nice Intro for Ingress... Thank you.
Thanks a lot for this great demo Sir. Can you please upload a similar demo for bare metal deployment of Ingress as it is different from on cloud ?
+1
best explanation.
Thank you.
Excellent actually!!
Awesome stuff! Thanks
can we bind the loadbalancer with the domain name at the time of creation instead of doing it in route 53
Thanks, Great Webinar. :-)
Can you please make a video how to enable ingress on promises
Make a video on how to make external ip address and cluster ip address static even though after re creating my service
Where is webinar for Building CI/CD Pipelines pls?
Can we us e a single ingress to direct to two services in two namespaces? Please do reply
Thanks! echoserver demo useful debugging feature.
Why did you stop your webinars ?
Good one
5 people like to spin up a load balancer per service
Nice video. Can you do one on TLS, ingress and name-based routing? There is a great ingress topic on let's encrypt that gets little coverage :)
Awesome
very good. do you have a git project.
How to remove ingress..?
I love you
Excellent video.
How does github.com/kubernetes/ingress-nginx fit into the picture?
Could you give us some real life use cases for it?
Thanks.
/A
Hi Paulo. This is a Ingress Controller, that controls how Ingress works and provides additional resources to use within your ingressses like "Annotations". The one that you mention is built on top of nginx. The Ingress Controller is deployed as a DaemonSet and looks on the apiserver's "/ingresses" endpoint for existing ingress definitions. WIth this information the Ingress Controller can use the cloud API to provide the IP from the Cloud Load Balancer used in the ingress, permiting external access. The ingress itself is just a definition that connects the external world outside the cluster to the services/pods inside it, but additional logic is required to make your cloud to see what's visible. The Ingress Controller is responsible for doing the other things to make this internal world accessible over the ingress. Using GKE or AKS kubernetes clusters the Ingress Controller is created automatically, so when you create a new ingress, the ingress Controller watch this creation and quickly create the necessary configurations in your cloud to viabilize the external access. In Bare-metal deployments, you must deploy the Ingress Controller for the ingress resource to work correctly.