1

00:00:00,300 --> 00:00:07,410

That localhost excuse is obviously a temporary solution for local access, so to make Kobana application



2

00:00:07,410 --> 00:00:15,870

accessible properly with a proper gural, we will configure ingress, which is part of communities that



3

00:00:15,870 --> 00:00:23,900

basically manages routing of incoming requests, like from a browser to internal services in communities.



4

00:00:24,600 --> 00:00:31,170

So in our example, you would need to install and run ingress controller in your communities cluster



5

00:00:31,620 --> 00:00:38,850

so that you can configure ingress rules that will then report the incoming traffic to your application



6

00:00:39,510 --> 00:00:46,440

to understand the concept behind this in a cloud environment like manage community service or in a remote



7

00:00:46,440 --> 00:00:47,640

communities engine.



8

00:00:47,760 --> 00:00:49,020

How does this setup work?



9

00:00:49,030 --> 00:00:55,730

How will Ingress get that incoming request if it happens through Lenos node balancer?



10

00:00:56,040 --> 00:01:03,600

So in cloud platforms you have cloud providers own load balancer implementations that gets in front



11

00:01:03,600 --> 00:01:05,670

of the Ingenix Ingress controller.



12

00:01:05,670 --> 00:01:08,420

So that becomes the entry point in your cluster.



13

00:01:08,820 --> 00:01:10,110

So let's see how that works.



14

00:01:10,380 --> 00:01:18,010

Lenard's Node Balancer is, as the name says, a load balancer for your work nodes where nodes are the



15

00:01:18,050 --> 00:01:19,740

Lenos server instances.



16

00:01:20,160 --> 00:01:22,560

So say you have truly node instances.



17

00:01:23,070 --> 00:01:30,630

One runs a database application, in other runs a web server and you expose the web server using a public



18

00:01:30,630 --> 00:01:34,770

IP address so browser can send request directly to the Web server.



19

00:01:35,280 --> 00:01:38,280

The problem is you can't scale this application.



20

00:01:38,520 --> 00:01:42,720

If you suddenly start getting a lot of traffic, your web server will become a bottleneck.



21

00:01:42,900 --> 00:01:49,260

Also, if you make changes to the Web server like reboard, it's reconfigure it, etc., your application



22

00:01:49,260 --> 00:01:50,280

becomes unavailable.



23

00:01:50,550 --> 00:01:57,360

Instead, let's say you add a node balance in front that takes the incoming request in directed to the



24

00:01:57,360 --> 00:01:58,110

web server.



25

00:01:58,260 --> 00:02:04,290

So node balancer will get the public IP address and a Web server will be hidden away and accessible



26

00:02:04,320 --> 00:02:08,290

only at private IP from the load balancer itself.



27

00:02:08,730 --> 00:02:12,510

Now you can add multiple web servers under that load balancer.



28

00:02:12,510 --> 00:02:19,680

That load balancer can forward the requester so you can scale your application up and down without users



29

00:02:19,680 --> 00:02:21,090

even noticing anything.



30

00:02:21,820 --> 00:02:27,330

They have an entry point to your application that you set up once and just live it and it works.



31

00:02:27,660 --> 00:02:32,430

It's just there to accept the requests and then redirected to one of the Web servers.