1

00:00:00,360 --> 00:00:08,730

This is the solution we do for the demon sets a lab so for the first question we have to find out the



2

00:00:08,760 --> 00:00:17,780

total number of demon sets created and all named spaces so let's go to the terminal and run cube deal.



3

00:00:17,820 --> 00:00:26,530

Get the S which is short for Neiman sets and we'll use dash dash all these spaces and here you can see



4

00:00:26,530 --> 00:00:30,940

that there are two demon sets one for Q proxy and the other one for.



5

00:00:30,950 --> 00:00:31,540

We've met



6

00:00:34,630 --> 00:00:37,050

and both of them are in the cube system namespace



7

00:00:39,850 --> 00:00:44,380

with names faces are the demon sets and so we already check that it's in cubes of some namespace



8

00:00:50,080 --> 00:00:52,900

which of the below is a demon set.



9

00:00:52,900 --> 00:00:57,790

So we already check that as well we net as a set and the rest of them are not



10

00:01:07,970 --> 00:01:12,370

on how many nodes are the parts should you buy the demon said CU proxy.



11

00:01:13,340 --> 00:01:19,440

So as per the definition the demon set will be created on all the nodes in the cluster.



12

00:01:19,580 --> 00:01:26,140

But let's take that anywhere we'll run cube it will get nodes that are two nodes in this cluster and



13

00:01:26,140 --> 00:01:36,790

next Let try cube deal dash and cube system get ports and grep for Q proxy



14

00:01:42,110 --> 00:01:43,510

and we have two ports.



15

00:01:44,090 --> 00:01:51,080

Let's send that a little further by using the white to show the different nodes in which the ports are



16

00:01:51,150 --> 00:01:51,500

scheduled.



17

00:01:51,530 --> 00:01:58,610

So here you can see that it's schedule on Master and nodes or 1 so the answer is to



18

00:02:02,680 --> 00:02:05,680

what is the image used by the port deployed by D.



19

00:02:05,700 --> 00:02:07,030

We have net demon set



20

00:02:12,380 --> 00:02:23,300

so to do this we will run cube CDL dash and cube system describe Newman said we have net and we can



21

00:02:23,300 --> 00:02:31,640

grab for the image so you can see there are two images because it gives us two containers but we can



22

00:02:32,180 --> 00:02:34,670

see which one is present and the option



23

00:02:38,470 --> 00:02:40,050

so we have the Vive cube.



24

00:02:40,060 --> 00:02:41,380

Two point six George Soros.



25

00:02:41,380 --> 00:02:42,510

So that's the correct answer.



26

00:02:44,580 --> 00:02:52,410

Deploy a demon set forth through Andy logging and use these given specification so the name of the demon



27

00:02:52,410 --> 00:02:58,450

set us elastic search so we can use the cube when it is documentation for this.



28

00:02:58,470 --> 00:03:04,560

So just look up a demon set and the documentation and that is an example which you can use if you want



29

00:03:04,560 --> 00:03:05,550

to create the demon set.



30

00:03:05,550 --> 00:03:11,860

You can also copy some of the fields from the documentation but there is also another way to do this



31

00:03:12,080 --> 00:03:20,790

one we'll see that in just a moment so another way to do it is to use cube steel create deployment give



32

00:03:20,790 --> 00:03:26,130

the name of the deployment or in this case the daemon set which is the last six search and provide the



33

00:03:26,130 --> 00:03:36,130

image name which is flowing the elastic search one point to zero and will make use of the dash dash



34

00:03:36,130 --> 00:03:39,380

dry run dash or Yama and redirect it to a file.



35

00:03:39,390 --> 00:03:41,610

So we are not essentially creating the deployment.



36

00:03:41,640 --> 00:03:50,190

We are just creating a Yammer format which we will edit later to creator and even set so here.



37

00:03:50,220 --> 00:03:51,730

The file is elastic not Yama.



38

00:03:51,880 --> 00:03:58,890

And now let's go into the file using we I text editor and change the kind from deployment to daemon



39

00:03:58,900 --> 00:04:07,460

set and there are a couple of other fields which we will edit as well but this is my strict to create



40

00:04:07,460 --> 00:04:14,250

a demon set because there's no imperative way to do it so next let's see the replicas too.



41

00:04:14,610 --> 00:04:15,780

Let's delete that field.



42

00:04:16,750 --> 00:04:23,010

Yeah but before that let's put the namespace as cubes assume because that's expected for the question.



43

00:04:23,010 --> 00:04:30,910

Delete the replicas field delete the strategy because a demon that does not use a strategy and then



44

00:04:30,970 --> 00:04:34,060

delete any other extra field that's not required.



45

00:04:36,910 --> 00:04:38,150

So this looks all right.



46

00:04:38,150 --> 00:04:40,640

You can compare it with the documentation as well.



47

00:04:40,640 --> 00:04:47,540

So essentially what you can do is in this case we have to add the namespace but remove the replicas



48

00:04:47,840 --> 00:04:52,190

and the strategy change the kind to daemon set and you should be good to go



49

00:04:55,410 --> 00:05:01,970

see the file and create the daemon said using cubes still apply that Sheriff elastic ammo there you



50

00:05:02,000 --> 00:05:03,770

go the demon that has been created.



51

00:05:03,960 --> 00:05:09,960

We can check the status using cube teal dash and cube system get even set



52

00:05:21,540 --> 00:05:26,380

let's check the answer.



53

00:05:26,610 --> 00:05:27,960

That was the last question.



54

00:05:27,960 --> 00:05:34,230

The final seven question is just an information so we will be using complex demon sets later in the



55

00:05:34,230 --> 00:05:41,940

course to click okay and blab as John thank you for joining me in this video.



56

00:05:41,950 --> 00:05:43,540

I'll see you and the next one.