1

00:00:00,640 --> 00:00:05,250

This is the solution video for the Deployment's lab.



2

00:00:07,520 --> 00:00:12,170

So the first question, again, we have to determine the number of ports running in the system.



3

00:00:13,440 --> 00:00:17,070

So let's go to the Domhnall and Ron Kuby still get pots.



4

00:00:18,370 --> 00:00:20,230

So there are no polls running right now.



5

00:00:24,340 --> 00:00:26,000

How many replica sets exist?



6

00:00:26,260 --> 00:00:29,740

So, again, let's try to get replica sets.



7

00:00:33,590 --> 00:00:34,640

The answer is zero.



8

00:00:37,740 --> 00:00:44,310

Now, how many deployments run on the system, so let's run Kubasik, you'll get deployments and the



9

00:00:44,310 --> 00:00:45,390

answer is still zero.



10

00:00:48,640 --> 00:00:51,050

How many deployments exist on the system now?



11

00:00:51,740 --> 00:00:56,890

It appears a few deployments have been created, so let's run the same command again and check.



12

00:00:58,090 --> 00:01:04,360

So right now, we can see that a new deployment by the name of front and dash deployment has been created.



13

00:01:04,480 --> 00:01:06,250

So the answer should be one.



14

00:01:10,430 --> 00:01:13,320

How many replica sets exist, so let's find.



15

00:01:13,790 --> 00:01:20,420

You'll get replica sets and we see that replica set has been created by the deployment.



16

00:01:21,430 --> 00:01:23,110

So there should be one.



17

00:01:24,430 --> 00:01:26,680

How many pots exist on the system now?



18

00:01:27,600 --> 00:01:29,860

Let's try and get pots.



19

00:01:31,130 --> 00:01:34,360

I can see that there are four parts which are in the cluster.



20

00:01:35,560 --> 00:01:39,900

So the answer is four out of all the existing ports, how many already?



21

00:01:40,810 --> 00:01:46,720

So you can see that all of them have the status of irremediable zero or a one.



22

00:01:47,630 --> 00:01:50,080

Already, so the answer should be zero.



23

00:01:54,460 --> 00:02:01,690

What is the image used to create reports for the new deployment, so let's run the command to.



24

00:02:03,530 --> 00:02:09,770

Describe deployments, front and deployment and group for the image.



25

00:02:10,890 --> 00:02:14,340

You can see that the image was just busy, box eight eight eight.



26

00:02:17,210 --> 00:02:19,130

What do you think, the deployment is not ready?



27

00:02:21,760 --> 00:02:28,660

So to find this, let's try and get parts and we'll try and still describe I against one of the parts



28

00:02:28,660 --> 00:02:29,320

listed here.



29

00:02:32,470 --> 00:02:38,770

And if you look at the even section, we can see the reason why it failed, so it says here clearly



30

00:02:38,770 --> 00:02:39,190

that.



31

00:02:40,270 --> 00:02:45,520

The repository does not exist in Docker Hub for the Xbox 888.



32

00:02:46,370 --> 00:02:49,700

And as a result, it was not able to pull it.



33

00:02:52,900 --> 00:02:57,580

So the answer is the image of the Xbox 83 does not exist.



34

00:02:58,060 --> 00:03:06,000

Now let's create a new deployment using the deployment definition file provided a route and it appears



35

00:03:06,010 --> 00:03:07,680

as an issue of this will try to fix it.



36

00:03:11,160 --> 00:03:18,420

So let's first try to created using Kube still apply the F deployment definition, dash one document.



37

00:03:18,510 --> 00:03:25,470

And here we can see an error that says that deployment cannot be fun and we shouldn't be one.



38

00:03:26,790 --> 00:03:29,520

Or perhaps we won, and if you notice.



39

00:03:32,250 --> 00:03:35,770

The word deployment is spelled with lowercase D, which is incorrect.



40

00:03:35,840 --> 00:03:42,720

Will change that and change to change it to uppercase D. So save the file and let's try to run the command



41

00:03:42,720 --> 00:03:43,080

again.



42

00:03:43,080 --> 00:03:45,020

And this time it has been successful.



43

00:03:48,270 --> 00:03:54,780

Now create a new deployment with the blue attributes using your own deployment definition for the name



44

00:03:54,780 --> 00:03:57,960

should be SCDP different and should have three replicas.



45

00:03:57,960 --> 00:04:02,010

And he made a SCPD two point four nine.



46

00:04:03,450 --> 00:04:04,620

So let's copy.



47

00:04:07,950 --> 00:04:11,350

And will you still create deployment?



48

00:04:11,760 --> 00:04:13,210

I'm just going to copy it.



49

00:04:13,230 --> 00:04:15,810

That's the name of the deployment, which is front end.



50

00:04:16,590 --> 00:04:23,450

And the image will make as of dash dash image is equal to a city PD.



51

00:04:23,460 --> 00:04:27,030

Two point four macalpine replica should be three.



52

00:04:28,120 --> 00:04:34,540

So let's add that flack so far of first, let's just create the deployment it will create but just one



53

00:04:34,690 --> 00:04:42,250

part and we can scale it using the capacity of scale deployment dash replicas and the name of the deployment.



54

00:04:44,750 --> 00:04:50,990

So now we should have the deployment ready with three replicas that can verify that using you'll still



55

00:04:50,990 --> 00:04:57,440

get deployments as the front end and here we can see that it is up and running with three pods.



56

00:05:02,270 --> 00:05:03,410

So that's it.



57

00:05:03,440 --> 00:05:05,870

Thank you for joining me and the solution we do.



58

00:05:05,900 --> 00:05:06,980

I'll see you in the next one.