1

00:00:00,640 --> 00:00:07,540

This is the solution video for the multiple schedulers lab, so the first question, what is the name



2

00:00:07,540 --> 00:00:12,310

of the pod that deploys the default, the scheduler and the environment?



3

00:00:13,900 --> 00:00:22,270

So to find this, let us go to the Domhnall and type Kubasik, we'll get parts on the system namespace.



4

00:00:24,580 --> 00:00:30,300

So that should you, as part of the control plane and as deployed and the collapse of some space, and



5

00:00:30,310 --> 00:00:36,160

here you can see that the name of the scheduler is called Kupe Scheduler Master.



6

00:00:38,060 --> 00:00:43,330

And this is deployed as a static port, so let's select that as our answer.



7

00:00:48,620 --> 00:00:54,770

Was the image used to deploy the equivalent of scheduler and to find this field on our describe against



8

00:00:54,770 --> 00:00:55,250

the port?



9

00:01:04,340 --> 00:01:08,480

And let's use the clip, come on, and wait for the image.



10

00:01:12,770 --> 00:01:20,660

And here we have the image, which is chaos or discord or I'll slash Kupe scheduler Beaujon one, not



11

00:01:20,660 --> 00:01:21,170

one eight.



12

00:01:26,660 --> 00:01:33,140

Next, we have to deploy an additional scheduler to the cluster using the specification on the right.



13

00:01:33,200 --> 00:01:36,630

So it has to be deployed in the same namespace as well.



14

00:01:37,160 --> 00:01:39,510

The name should be my scheduler.



15

00:01:40,040 --> 00:01:44,930

It should have the custom scheduler name and it should be in the running street.



16

00:01:45,950 --> 00:01:51,950

We can use the manifest file used by the Cupido to deploy the default the scheduler.



17

00:01:54,520 --> 00:02:02,050

Secure Adam Tool deploys the scheduler on other controlled plane components by making use of manifest



18

00:02:02,050 --> 00:02:06,880

file, which is by default and the sequence this manifest directly.



19

00:02:07,780 --> 00:02:09,370

So let's go there first.



20

00:02:13,370 --> 00:02:16,740

And here we have a file called Cube does do document.



21

00:02:17,270 --> 00:02:18,380

So let's copy that.



22

00:02:22,490 --> 00:02:30,380

And we'll copy that to the route, but we'll also rename the file to my dad's or document.



23

00:02:36,750 --> 00:02:42,230

So now I'm back to slash food and let's edit our mind to learn of.



24

00:02:44,110 --> 00:02:51,280

Before we make any changes, let's go to the Corners documentation and look at the official docs for



25

00:02:52,090 --> 00:02:53,830

creating multiple schedules.



26

00:02:54,460 --> 00:02:57,190

I'm just going to search for multiple scheduler.



27

00:03:01,540 --> 00:03:06,690

And here we have a link that says Configure multiple Muslim communities.



28

00:03:06,690 --> 00:03:11,110

So let's click on that and let's scroll down to the definition.



29

00:03:11,680 --> 00:03:18,190

So here we have an example where the the scheduler or an additional governor, the scheduler has been



30

00:03:18,190 --> 00:03:22,510

deployed, has been deployed as this deployment.



31

00:03:24,460 --> 00:03:31,270

And here we have the definition for the second rule, binding sex, which we do not have to do in this



32

00:03:31,270 --> 00:03:39,090

case because we are making use of the definition file, which we have copied from the benefits category,



33

00:03:39,190 --> 00:03:41,690

which is when it is manifest.



34

00:03:41,710 --> 00:03:43,300

We will not have to do any of these.



35

00:03:43,630 --> 00:03:46,690

But let's go and check out the definition FIGLIA.



36

00:03:48,100 --> 00:03:55,810

So here we have the command section for the containers and we can see that there are two options that



37

00:03:55,810 --> 00:03:56,620

we have to consider.



38

00:03:56,650 --> 00:04:02,110

One is the leader elect should be the default and then the scheduler name that we have to specify,



39

00:04:02,140 --> 00:04:04,900

which is also in this case, where the scheduler.



40

00:04:05,260 --> 00:04:08,260

So let's copy those two lines from here.



41

00:04:11,920 --> 00:04:19,390

In fact, the relict command is already there, it is set to true, but we can't use that to follow.



42

00:04:19,440 --> 00:04:21,220

So let's go all the way down



43

00:04:24,250 --> 00:04:27,790

to the command section and I'm going to change it to false.



44

00:04:28,690 --> 00:04:31,060

And it's this page.



45

00:04:32,140 --> 00:04:33,820

You should the name should be mine.



46

00:04:33,820 --> 00:04:39,780

I should look let's see the name of the pod to my right scheduler as well.



47

00:04:41,240 --> 00:04:45,590

And while we're at it, let's also change the name of the container.



48

00:04:45,860 --> 00:04:49,760

It's not necessary, but it does change it.



49

00:04:51,640 --> 00:04:53,910

And everything else should be OK.



50

00:04:55,230 --> 00:04:58,710

And in accordance with the documentation.



51

00:05:01,020 --> 00:05:06,150

So let's go ahead and create this custom scheduler by the name of my scheduler.



52

00:05:11,420 --> 00:05:13,760

You can see that the port has been created.



53

00:05:13,870 --> 00:05:23,360

It's wrong to get parts of the tube system namespace again and the bottom, we can see that the Midas



54

00:05:23,360 --> 00:05:26,690

scheduler part has been created and it doesn't enough running street.



55

00:05:29,170 --> 00:05:31,020

So let's validate our answer.



56

00:05:35,260 --> 00:05:42,220

So for the final question, the definition is given, use it to create a part with the new costume scheduler



57

00:05:42,700 --> 00:05:48,710

and the definition is located at Slashdot and the next dashboard odioma.



58

00:05:50,680 --> 00:05:52,820

So it should make use of the customary.



59

00:05:58,860 --> 00:06:01,140

So here is our definition file.



60

00:06:01,440 --> 00:06:08,290

So in order to make use of our customary law that we just created will add a new field under the special



61

00:06:08,340 --> 00:06:12,420

section called Scheduler Name and the name of the scheduler.



62

00:06:14,590 --> 00:06:16,210

Now, let's create this blog.



63

00:06:22,650 --> 00:06:25,950

And let's take this tweet us using Kubasik, they'll get Pott's.



64

00:06:28,380 --> 00:06:30,270

Does and contain accreting said.



65

00:06:32,680 --> 00:06:39,340

I'm just using this watch command here just to make sure that it takes to see every two seconds, I



66

00:06:39,340 --> 00:06:44,500

know it's already in I'm running state, so I'm going to control all of this.



67

00:06:45,850 --> 00:06:48,460

And while we're at it, let's try and keep still.



68

00:06:48,460 --> 00:06:50,290

Describe what?



69

00:06:52,490 --> 00:06:53,480

Ingenix.



70

00:06:55,920 --> 00:07:02,620

And here we can see that it has made use of the Midas scheduler to assign the part called the engine



71

00:07:02,620 --> 00:07:06,620

next to another one, and it is now running shape.



72

00:07:06,640 --> 00:07:10,680

So that should be the end of this solution.



73

00:07:10,710 --> 00:07:11,130

We do.



74

00:07:12,230 --> 00:07:14,860

Thank you for joining me and I'll see you in the next one.