1

00:00:00,580 --> 00:00:07,120

In order to deploy fluent, the demon said, we're going to use Helme charts again.



2

00:00:07,140 --> 00:00:11,090

I found a fluent Helme chart from Pete Nemi.



3

00:00:11,110 --> 00:00:15,460

Obviously, there are a bunch of different charts from different maintainers.



4

00:00:16,060 --> 00:00:19,270

So I'm going to just go with this one again.



5

00:00:19,270 --> 00:00:20,620

Already familiar steps.



6

00:00:21,070 --> 00:00:25,870

So first, we're going to add a bit Nemi repository so that we can access the charts.



7

00:00:26,470 --> 00:00:27,340

So let's do that.



8

00:00:27,640 --> 00:00:33,410

Repository has been added and we can install the chart.



9

00:00:33,430 --> 00:00:35,930

Let's actually call it fluid.



10

00:00:42,780 --> 00:00:48,960

And it was installed, let's actually see what components got created and what actually happened.



11

00:00:49,950 --> 00:00:56,910

And here you see there are four different containers of 20 to get a better overview of what components



12

00:00:56,910 --> 00:00:57,520

got created.



13

00:00:57,540 --> 00:01:02,970

I would go to the dashboard and here you see in a different namespace, the containers are starting



14

00:01:02,970 --> 00:01:03,240

up.



15

00:01:03,570 --> 00:01:09,870

First thing we see is a demon said God created and here are the pots.



16

00:01:09,870 --> 00:01:11,790

So two of them just got created.



17

00:01:11,790 --> 00:01:13,500

One of them is still starting.



18

00:01:17,070 --> 00:01:22,950

And here, as you see, a state full set of fluency also created.



19

00:01:24,470 --> 00:01:31,010

Here we have a bunch of fluidity services and so on, the good thing about Helme chards is that you



20

00:01:31,010 --> 00:01:34,340

don't have to know all the components.



21

00:01:34,440 --> 00:01:36,770

You have to understand how this whole thing works.



22

00:01:37,140 --> 00:01:44,060

You can rely on the fact that they have correctly set it up and once you install it in your cluster,



23

00:01:44,360 --> 00:01:46,010

it will do its job.



24

00:01:46,040 --> 00:01:49,760

So basically, you don't have to understand what these things do.



25

00:01:50,300 --> 00:01:56,660

You have to understand how the application works and how you can configure what you need to configure,



26

00:01:56,660 --> 00:02:00,440

which is reading the logs and saving to ElasticSearch.



27

00:02:01,520 --> 00:02:03,440

So let's refresh it again.



28

00:02:03,440 --> 00:02:07,820

Here you see all the pods started and everything is running fine.