1

00:00:00,210 --> 00:00:06,750

This is the solution video for the pod slap, which is our very first lab, so the first question is



2

00:00:06,750 --> 00:00:14,370

for us to find out the number of parts that are existing in the system to do this will go back to the



3

00:00:14,370 --> 00:00:15,720

DOMHNALL and run the command.



4

00:00:15,720 --> 00:00:17,400

Kubek will get pods.



5

00:00:17,950 --> 00:00:21,290

And you can see that currently there are no ports running in the system.



6

00:00:23,390 --> 00:00:30,680

So the answer is zero and the next question, we had to create a new board with the engine image.



7

00:00:32,660 --> 00:00:39,350

Let's run the command cube CTA run in Ingenix Dash Dash image is equal to Ingenix.



8

00:00:41,070 --> 00:00:47,820

From government is one dot, one eight onwards, this command will create a pod and set off a deployment,



9

00:00:47,820 --> 00:00:50,160

which was true for previous versions.



10

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

So here we have a pod called Ingenix created to validate let's run CubeSat will get pods again.



11

00:00:58,500 --> 00:01:01,710

And you can see that it is in that container creating state.



12

00:01:04,160 --> 00:01:06,400

So let's go and validate the answer.



13

00:01:08,560 --> 00:01:14,140

And again, we have to check how many parts have been created in the system, so let's run the same



14

00:01:14,140 --> 00:01:15,160

command again.



15

00:01:16,460 --> 00:01:22,500

And now you'll notice that including our next part, a few more ports have been created.



16

00:01:22,520 --> 00:01:26,030

So in total, there are four which are running on this cluster now.



17

00:01:29,390 --> 00:01:32,270

And all of them are in the running states, so the answer is for.



18

00:01:34,830 --> 00:01:40,530

What is the image used to create the new pots and for this, we'll have to look into the description



19

00:01:40,530 --> 00:01:41,190

of the pot?



20

00:01:42,970 --> 00:01:49,180

So let's copy one of these parts and we will clear the screen and on the command cube cubicle, describe



21

00:01:49,180 --> 00:01:51,580

pod and the name of the pod.



22

00:01:54,130 --> 00:01:56,440

And let's grab for the image.



23

00:01:58,070 --> 00:02:01,130

Here we can see that the image used this busy box.



24

00:02:03,740 --> 00:02:05,930

So let's say select Zyvox.



25

00:02:07,630 --> 00:02:09,840

Which notes are these parts, please, John?



26

00:02:10,300 --> 00:02:12,400

So, again, let's go back to the terminal.



27

00:02:15,780 --> 00:02:24,120

And will run the command, Kubek will get parts with the dash, all white option, and this will show



28

00:02:24,120 --> 00:02:26,950

us the north and west deposal place.



29

00:02:26,970 --> 00:02:31,140

So here we can see that all the pods are running on node 01.



30

00:02:33,430 --> 00:02:35,340

So let's select that as the answer.



31

00:02:38,140 --> 00:02:43,450

Now we have to find out the containers that are part of one new port called Webapp.



32

00:02:47,090 --> 00:02:56,120

So first, let's run Gibbsville get web app and can see that under the ready column, we can see one



33

00:02:56,120 --> 00:03:00,470

out of two, which is an indicator that there are two containers running and that port.



34

00:03:04,260 --> 00:03:08,730

We along, we had to find out what images are used for the new Web board.



35

00:03:11,240 --> 00:03:17,270

So let's run the command cubicle, describe pod webapp.



36

00:03:18,720 --> 00:03:24,690

And if you scroll up, we should be able to see these containers which have been created, so there



37

00:03:24,690 --> 00:03:30,070

is one called Agent X and there is another one called Engine X.



38

00:03:30,070 --> 00:03:33,000

So there are two containers which are part of this pod.



39

00:03:40,090 --> 00:03:44,140

What is the state of the container agent X and the port webapp?



40

00:03:45,210 --> 00:03:49,420

Again, we can make use of the same comment as before, which is the described come on.



41

00:03:49,690 --> 00:03:51,790

And you can see that the state is waiting.



42

00:03:55,650 --> 00:03:57,420

So let's select error or wait.



43

00:03:58,410 --> 00:04:02,440

Why do you think the container agent X and the port webapp is in error?



44

00:04:04,350 --> 00:04:08,360

So again, we should be able to find that out from the evil section.



45

00:04:09,510 --> 00:04:17,670

So here we can see that the agent X image could not be pulled out from our dock, Rob, because such



46

00:04:17,670 --> 00:04:19,140

an image does not exist.



47

00:04:26,280 --> 00:04:31,000

What is the red column in the output of Kubek will get parts come indicate.



48

00:04:31,980 --> 00:04:37,290

So we have already seen that the previous question, so let's run.



49

00:04:37,590 --> 00:04:39,350

It will get past webapp again.



50

00:04:39,360 --> 00:04:41,740

And here you can see that the column is ready.



51

00:04:42,060 --> 00:04:46,560

So this shows the number of containers running containers.



52

00:04:48,250 --> 00:04:56,140

In the pod, two running containers in the port, which as compared to the total containers in the pod.



53

00:04:57,100 --> 00:05:03,580

So let's not delete the pod called webapp and to do this will run capacity or delete pod web app.



54

00:05:09,140 --> 00:05:10,520

The port has been deleted.



55

00:05:14,000 --> 00:05:18,820

Now let's create a new pod with the name Redus, and the image right is one, two, three.



56

00:05:19,310 --> 00:05:23,990

So this image does not exist, but the respective puppet and create this pod.



57

00:05:27,530 --> 00:05:29,540

So let's use the same commanders before.



58

00:05:31,380 --> 00:05:37,950

We use Kubek Children, Reader's Digest, our image is equal to readers, one, two, three.



59

00:05:47,150 --> 00:05:50,370

But first, we'll make use of dry run is equal to client.



60

00:05:50,570 --> 00:05:52,100

This will allow us to.



61

00:05:54,130 --> 00:05:56,980

Create a dry run of the pot.



62

00:05:57,010 --> 00:06:05,770

It will not create the pot, but we can use Oyamel to redirect the YAML definition into a file called



63

00:06:05,770 --> 00:06:06,040

pot.



64

00:06:08,570 --> 00:06:11,810

So let's open up this file using the editor.



65

00:06:13,790 --> 00:06:20,600

And you can see that in this case, we have a pod called Red is the name of the container is also released,



66

00:06:20,600 --> 00:06:22,730

but it's using a wrong image called Redus.



67

00:06:22,730 --> 00:06:23,540

One, two, three.



68

00:06:26,070 --> 00:06:27,360

So let's save this file.



69

00:06:31,540 --> 00:06:40,870

And created using Kubek to apply the F and name of the poor definition for just Baudot yaml, it's now



70

00:06:40,870 --> 00:06:42,220

the part has been created.



71

00:06:44,830 --> 00:06:46,480

So let's go back and check.



72

00:06:48,840 --> 00:06:52,350

Now, finally, we have to fix the image on the iPod Redus.



73

00:06:56,690 --> 00:07:01,280

And to do this, we will use Kubek edit Pod Redus.



74

00:07:02,710 --> 00:07:10,330

That should open up the running configuration and we, Ed, and let's scroll all the way to the bottom



75

00:07:10,330 --> 00:07:15,430

and find the feel called image and will change it from readers want to try to read reduce.



76

00:07:17,250 --> 00:07:19,590

Was the Susanville safe before?



77

00:07:21,540 --> 00:07:27,660

And that should be it, the response should be updated now with the correct image, which is also called



78

00:07:27,780 --> 00:07:28,350

Redus.



79

00:07:29,810 --> 00:07:30,600

So give it a minute.



80

00:07:30,620 --> 00:07:34,670

So now it's in our state and that should be the end.



81

00:07:34,700 --> 00:07:35,820

That's our last question.



82

00:07:35,840 --> 00:07:37,730

So thank you for joining me in this video.



83

00:07:37,760 --> 00:07:38,990

I'll see you in the next one.