So first, we'll need to install Ingress controller in the cluster, and we're also going to do that
using help their different ingress controllers for communities like there is Ingenix ingress from Bernardes
itself and there is Ingenix ingress from News Corp and so on.
And we're going to install Coronado's Ingenix Engross controller.
And there is a chart for that.
And we're going to go through the similar process.
We're going to add the repositories that hold the chart.
So it's to help Grippo Ed.
And in this case, we're going to add two repositories, actually.
So this is the first one and another one.
Like this, you can also see all these comments in the git repository that I provided, so you can just
copy the comments from there and now the repositories are added.
We can actually install the help chart.
So help install and we're going to call it Ingenix Ingress and the repository of the chart and the name
of the chart.
And this should actually install Ingenix Ingress controller, you know, cluster.
And here you see the output, it was installed and we have some example configuration file here.
So now if I do, it'll get power.
I should see the Ingenix increase controller pod actually running in the cluster.
It's still creating and now it's running.
And as I mentioned in the previous video, Englis controller uses the cloud netiv load balancer or in
this case, Alino to node balancer.
So if I go back to Lehnert to node balancers, I can see that one node balancer was created dynamically
as I deployed the Ingress controller.
So these two are tied together, connected together.
And here you see it has a public IP address.
So Node Balancer and its IP address will be an entry point to our cluster.
So the browser request will first lend a node balancer, which will then forward it or hand it over
to our Ingenix Ingress controller.
Based on that rule, Ingenix Ingress will decide which internal service to forward that request to.
So that's how the request flow will work.