WEBVTT 00:00.640 --> 00:05.250 This is the solution video for the Deployment's lab. 00:07.520 --> 00:12.170 So the first question, again, we have to determine the number of ports running in the system. 00:13.440 --> 00:17.070 So let's go to the Domhnall and Ron Kuby still get pots. 00:18.370 --> 00:20.230 So there are no polls running right now. 00:24.340 --> 00:26.000 How many replica sets exist? 00:26.260 --> 00:29.740 So, again, let's try to get replica sets. 00:33.590 --> 00:34.640 The answer is zero. 00:37.740 --> 00:44.310 Now, how many deployments run on the system, so let's run Kubasik, you'll get deployments and the 00:44.310 --> 00:45.390 answer is still zero. 00:48.640 --> 00:51.050 How many deployments exist on the system now? 00:51.740 --> 00:56.890 It appears a few deployments have been created, so let's run the same command again and check. 00:58.090 --> 01:04.360 So right now, we can see that a new deployment by the name of front and dash deployment has been created. 01:04.480 --> 01:06.250 So the answer should be one. 01:10.430 --> 01:13.320 How many replica sets exist, so let's find. 01:13.790 --> 01:20.420 You'll get replica sets and we see that replica set has been created by the deployment. 01:21.430 --> 01:23.110 So there should be one. 01:24.430 --> 01:26.680 How many pots exist on the system now? 01:27.600 --> 01:29.860 Let's try and get pots. 01:31.130 --> 01:34.360 I can see that there are four parts which are in the cluster. 01:35.560 --> 01:39.900 So the answer is four out of all the existing ports, how many already? 01:40.810 --> 01:46.720 So you can see that all of them have the status of irremediable zero or a one. 01:47.630 --> 01:50.080 Already, so the answer should be zero. 01:54.460 --> 02:01.690 What is the image used to create reports for the new deployment, so let's run the command to. 02:03.530 --> 02:09.770 Describe deployments, front and deployment and group for the image. 02:10.890 --> 02:14.340 You can see that the image was just busy, box eight eight eight. 02:17.210 --> 02:19.130 What do you think, the deployment is not ready? 02:21.760 --> 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 02:28.660 --> 02:29.320 listed here. 02:32.470 --> 02:38.770 And if you look at the even section, we can see the reason why it failed, so it says here clearly 02:38.770 --> 02:39.190 that. 02:40.270 --> 02:45.520 The repository does not exist in Docker Hub for the Xbox 888. 02:46.370 --> 02:49.700 And as a result, it was not able to pull it. 02:52.900 --> 02:57.580 So the answer is the image of the Xbox 83 does not exist. 02:58.060 --> 03:06.000 Now let's create a new deployment using the deployment definition file provided a route and it appears 03:06.010 --> 03:07.680 as an issue of this will try to fix it. 03:11.160 --> 03:18.420 So let's first try to created using Kube still apply the F deployment definition, dash one document. 03:18.510 --> 03:25.470 And here we can see an error that says that deployment cannot be fun and we shouldn't be one. 03:26.790 --> 03:29.520 Or perhaps we won, and if you notice. 03:32.250 --> 03:35.770 The word deployment is spelled with lowercase D, which is incorrect. 03:35.840 --> 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 03:42.720 --> 03:43.080 again. 03:43.080 --> 03:45.020 And this time it has been successful. 03:48.270 --> 03:54.780 Now create a new deployment with the blue attributes using your own deployment definition for the name 03:54.780 --> 03:57.960 should be SCDP different and should have three replicas. 03:57.960 --> 04:02.010 And he made a SCPD two point four nine. 04:03.450 --> 04:04.620 So let's copy. 04:07.950 --> 04:11.350 And will you still create deployment? 04:11.760 --> 04:13.210 I'm just going to copy it. 04:13.230 --> 04:15.810 That's the name of the deployment, which is front end. 04:16.590 --> 04:23.450 And the image will make as of dash dash image is equal to a city PD. 04:23.460 --> 04:27.030 Two point four macalpine replica should be three. 04:28.120 --> 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 04:34.690 --> 04:42.250 part and we can scale it using the capacity of scale deployment dash replicas and the name of the deployment. 04:44.750 --> 04:50.990 So now we should have the deployment ready with three replicas that can verify that using you'll still 04:50.990 --> 04:57.440 get deployments as the front end and here we can see that it is up and running with three pods. 05:02.270 --> 05:03.410 So that's it. 05:03.440 --> 05:05.870 Thank you for joining me and the solution we do. 05:05.900 --> 05:06.980 I'll see you in the next one.