1

00:00:00,480 --> 00:00:06,990

Hello and welcome to the solution video for the practice tests where we are configuring resource limits



2

00:00:06,990 --> 00:00:09,440

and requests for pods and covenants.



3

00:00:09,900 --> 00:00:13,890

So for the first question a board named rabbit is deployed.



4

00:00:13,890 --> 00:00:19,350

Identify DCP requirements set on the pod the pod is in the default namespace



5

00:00:24,480 --> 00:00:32,880

so as you can see a pod has indeed been created for us called Rabbit now to identify the CPSU requirements.



6

00:00:32,880 --> 00:00:35,460

We will use the cube CTO described command



7

00:00:39,230 --> 00:00:44,630

if you scroll through to the container section you'll see that a container called zip use stress has



8

00:00:44,630 --> 00:00:52,990

been created and within that you would see that there is a limited section for CPI and a request.



9

00:00:53,000 --> 00:01:02,840

So the request in this case is one CPI and the limit as to CPI so for the part to be scheduled the minimum



10

00:01:02,840 --> 00:01:04,630

requirements for the CPI u.



11

00:01:04,670 --> 00:01:10,430

As for the worker to have at least one CPI so the correct answer here is 1



12

00:01:13,830 --> 00:01:14,240

next.



13

00:01:14,250 --> 00:01:15,540

We will delete the part



14

00:01:25,110 --> 00:01:32,970

and we'll wait for the port to terminate while we do that for additional reference you can use equal



15

00:01:32,970 --> 00:01:35,740

when it is documentation under the task section.



16

00:01:35,760 --> 00:01:43,470

There is a section called Ask configure pots and containers and thus you'll find two subsections useful



17

00:01:43,470 --> 00:01:44,620

one as a sign.



18

00:01:44,820 --> 00:01:53,200

Memory resources to port and the other one as assigned CPR resources so in addition to the lectures.



19

00:01:53,200 --> 00:02:03,760

This is a good source of reference for anything related to resource limits and requests so back to our



20

00:02:03,760 --> 00:02:08,140

terminal looks like the port a rabbit has been deleted so let's check



21

00:02:11,520 --> 00:02:13,720

now a new port has been deployed for us.



22

00:02:14,160 --> 00:02:16,860

It's called Elephant identified the status.



23

00:02:16,950 --> 00:02:19,380

Let's try and keep CDL get pods



24

00:02:22,730 --> 00:02:25,610

and you can see that as in a crash loop back off state



25

00:02:31,920 --> 00:02:38,460

if you see the reason it is out of memory killed and the state the last state US terminated



26

00:02:43,630 --> 00:02:51,040

the status or am killed or if memory killed indicates that the port ran out of memory identify the memory



27

00:02:51,040 --> 00:02:52,570

limit set on the port



28

00:02:57,510 --> 00:03:00,810

so here you can see that the memory limit is 10



29

00:03:04,610 --> 00:03:10,370

for the next question the elephant runs a process that consumes 15 MRI of memory.



30

00:03:10,460 --> 00:03:14,190

Increase the limit of the elephant port to 20.



31

00:03:14,480 --> 00:03:18,230

Delete and recreate the port if required do not modify anything else.



32

00:03:19,560 --> 00:03:21,600

So the name is elephant.



33

00:03:21,600 --> 00:03:32,240

The image name as peel Linux stress slash stress and the memory limit should be 20 so let's generate



34

00:03:32,250 --> 00:03:44,110

the pod definition file using cubes it'll get hot and we'll use dash or Yama and redirected to a file



35

00:03:49,700 --> 00:03:59,470

so in this case we are going to increase the memory limit to 20 let's delete the existing pod



36

00:04:04,620 --> 00:04:09,750

and we will create the new pod once the current one has been terminated



37

00:04:17,520 --> 00:04:24,030

and once we have the new port running usually describe command to make sure that the limit has indeed



38

00:04:24,030 --> 00:04:24,630

increased.



39

00:04:24,660 --> 00:04:25,830

So now it's 20



40

00:04:32,900 --> 00:04:34,730

and the pod is now in a running state



41

00:04:40,400 --> 00:04:43,100

delete the pod and wait for it to terminate



42

00:04:54,480 --> 00:04:56,330

so that was the last question.



43

00:04:56,340 --> 00:05:02,310

This is an easy enough lab and as I said before you can go through the reference documentation if you



44

00:05:02,310 --> 00:05:05,220

want to get more information related to this topic.



45

00:05:06,030 --> 00:05:09,180

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