1

00:00:00,440 --> 00:00:07,340

So first, we'll need to install Ingress controller in the cluster, and we're also going to do that



2

00:00:07,340 --> 00:00:13,880

using help their different ingress controllers for communities like there is Ingenix ingress from Bernardes



3

00:00:13,880 --> 00:00:18,230

itself and there is Ingenix ingress from News Corp and so on.



4

00:00:18,890 --> 00:00:22,970

And we're going to install Coronado's Ingenix Engross controller.



5

00:00:23,330 --> 00:00:24,920

And there is a chart for that.



6

00:00:25,460 --> 00:00:27,860

And we're going to go through the similar process.



7

00:00:27,860 --> 00:00:30,410

We're going to add the repositories that hold the chart.



8

00:00:30,590 --> 00:00:33,380

So it's to help Grippo Ed.



9

00:00:33,890 --> 00:00:37,050

And in this case, we're going to add two repositories, actually.



10

00:00:37,280 --> 00:00:40,490

So this is the first one and another one.



11

00:00:43,800 --> 00:00:50,220

Like this, you can also see all these comments in the git repository that I provided, so you can just



12

00:00:50,220 --> 00:00:53,760

copy the comments from there and now the repositories are added.



13

00:00:54,000 --> 00:00:55,750

We can actually install the help chart.



14

00:00:56,700 --> 00:01:06,300

So help install and we're going to call it Ingenix Ingress and the repository of the chart and the name



15

00:01:06,300 --> 00:01:06,800

of the chart.



16

00:01:07,200 --> 00:01:11,580

And this should actually install Ingenix Ingress controller, you know, cluster.



17

00:01:12,520 --> 00:01:18,560

And here you see the output, it was installed and we have some example configuration file here.



18

00:01:18,850 --> 00:01:21,670

So now if I do, it'll get power.



19

00:01:22,030 --> 00:01:28,210

I should see the Ingenix increase controller pod actually running in the cluster.



20

00:01:28,220 --> 00:01:32,530

It's still creating and now it's running.



21

00:01:33,280 --> 00:01:40,360

And as I mentioned in the previous video, Englis controller uses the cloud netiv load balancer or in



22

00:01:40,360 --> 00:01:42,260

this case, Alino to node balancer.



23

00:01:42,550 --> 00:01:51,520

So if I go back to Lehnert to node balancers, I can see that one node balancer was created dynamically



24

00:01:51,880 --> 00:01:55,060

as I deployed the Ingress controller.



25

00:01:55,090 --> 00:01:58,190

So these two are tied together, connected together.



26

00:01:58,540 --> 00:02:01,140

And here you see it has a public IP address.



27

00:02:01,330 --> 00:02:07,470

So Node Balancer and its IP address will be an entry point to our cluster.



28

00:02:07,990 --> 00:02:14,290

So the browser request will first lend a node balancer, which will then forward it or hand it over



29

00:02:14,290 --> 00:02:17,040

to our Ingenix Ingress controller.



30

00:02:17,350 --> 00:02:26,590

Based on that rule, Ingenix Ingress will decide which internal service to forward that request to.



31

00:02:27,070 --> 00:02:30,210

So that's how the request flow will work.