1

00:00:00,210 --> 00:00:06,480

So now we have ElasticSearch running so we can install second component of elastic steak, which is



2

00:00:06,480 --> 00:00:10,730

Cubano and Elastic also has a hem chart for Caivano.



3

00:00:11,070 --> 00:00:12,150

So you click here.



4

00:00:12,930 --> 00:00:17,180

This is also official one and super simple installation.



5

00:00:17,490 --> 00:00:22,460

You also have a list of configuration or parameters here, but we don't need to overwrite anything.



6

00:00:22,470 --> 00:00:26,750

So we're just going to go with the comment without any external parameters.



7

00:00:27,030 --> 00:00:30,300

So this should install Caivano deployment.



8

00:00:31,460 --> 00:00:34,720

And all necessary components that it needs.



9

00:00:35,330 --> 00:00:37,460

Again, let's check it hot.



10

00:00:38,950 --> 00:00:44,890

And the container is creating, of course, Cubano compared to ElasticSearch is not a stateful application



11

00:00:44,890 --> 00:00:46,880

because it doesn't have a state of its own.



12

00:00:47,110 --> 00:00:49,960

It gets all of its data from ElasticSearch.



13

00:00:50,200 --> 00:00:57,940

So Kibwana replication and configuration is pretty easy compared to elastic, and therefore it also



14

00:00:57,940 --> 00:01:00,760

gets created as a deployment and not a stateful said.



15

00:01:00,770 --> 00:01:10,120

So we can also go back to dashboard and refresh and here you see the status dashboard, so to say,



16

00:01:10,390 --> 00:01:15,370

when a pod is just starting up, you have these different colors.



17

00:01:15,760 --> 00:01:16,750

So if you refresh.



18

00:01:17,760 --> 00:01:24,480

Everything is green, so Kibwana is running and as I said, it is a deployment component and we just



19

00:01:24,480 --> 00:01:27,560

have one replica of it, carbonised UI.



20

00:01:27,570 --> 00:01:31,190

So obviously we want to see how it looks, how its dashboard looks.



21

00:01:31,500 --> 00:01:37,000

So if we scroll down to the services, you see there is a Kibwana service right here.



22

00:01:37,800 --> 00:01:40,990

However, it is of cluster ipe type means.



23

00:01:41,010 --> 00:01:46,270

It is an internal service so it doesn't allow external or browser requests to it.



24

00:01:46,890 --> 00:01:52,860

So later we're going to configure ingress for it so that we can access it through a browser.



25

00:01:53,070 --> 00:02:01,050

But there's a hitch or a test set up, so to say, where you can access internal services from a remote



26

00:02:01,050 --> 00:02:05,010

cluster, for example, through your local host on your laptop.



27

00:02:05,310 --> 00:02:08,450

And the way to do that is using cubes.



28

00:02:08,460 --> 00:02:17,810

It'll put forward a deployment, keep on the name.



29

00:02:18,150 --> 00:02:24,150

And here we just need the port where the application is running, which we can see here.



30

00:02:24,660 --> 00:02:33,180

This is the endpoint in port and which will forward the requests from our local host to that internal



31

00:02:33,180 --> 00:02:33,610

service.



32

00:02:33,900 --> 00:02:42,790

So now if I do localhost the ports that I copied, I should be able to see Cubano Dashboard on my laptop.



33

00:02:42,810 --> 00:02:48,570

So this is a dashboard and you have access to different tools, but we're not going to be able to see



34

00:02:48,570 --> 00:02:51,070

anything because our elasticsearch is empty.



35

00:02:51,660 --> 00:02:55,970

So that's how you can access internal services on localhost.



36

00:02:56,340 --> 00:02:59,510

Know that obviously this only works on your laptop.



37

00:02:59,520 --> 00:03:05,790

So for a long term solution, if your whole team needs access to Kibwana or you want to have its own



38

00:03:05,790 --> 00:03:06,700

endpoint for it.



39

00:03:06,960 --> 00:03:11,370

So in that case, we'll need to configure ingress, which we are going to do in the next section.