WEBVTT 00:00.600 --> 00:03.500 In this demo, we're going to create a deployment. 00:04.280 --> 00:11.720 So let us create a new folder called Deployments within our project directory and within the deployments 00:12.050 --> 00:12.590 directory. 00:12.620 --> 00:17.630 I'm going to create a new file called ADD called Deployment That YAML. 00:20.240 --> 00:26.220 And we're going to make use of the definition file that we created earlier for the replica assets because 00:26.220 --> 00:28.320 it's quite similar to that after deployment. 00:28.620 --> 00:32.420 And to make this easier, we're just going to open the replica set definition file. 00:33.180 --> 00:33.900 On the right. 00:34.800 --> 00:37.740 So I'm going to use the split ed function here. 00:38.730 --> 00:43.110 So on the left, we have the deployment of the ammo file that we're going to create now. 00:43.200 --> 00:47.040 And on the right, we have the replica, said Don YAML file that we created earlier. 00:49.100 --> 00:51.990 So, as before, we will start off with the API version. 00:52.350 --> 00:57.570 And it is and it is also going to be apps slash me one and the same as Republicans said. 00:58.830 --> 01:01.200 And I'm going to use the kind as deployment. 01:02.100 --> 01:06.480 So let me select that from here and then the metadata. 01:06.780 --> 01:08.970 I'm going to enter it here as well. 01:09.000 --> 01:12.840 And that will have the name and labels. 01:12.930 --> 01:19.700 And we're going to use the name as my app Dash. 01:19.800 --> 01:20.400 Deployment. 01:21.880 --> 01:25.750 And I will add a couple of labels as well. 01:28.880 --> 01:38.120 The labels will be front end to your front end and maybe another one called Engine X. 01:39.280 --> 01:39.580 OK. 01:40.340 --> 01:44.250 Now the specked section is very similar to that of the replica set. 01:44.390 --> 01:50.480 So I'm just going to copy this entire section here for the specs, for the spec section, and I'm just 01:50.480 --> 01:51.890 going to paste it here. 01:52.820 --> 01:55.820 So that should be good enough for us to start the deployment. 01:56.030 --> 02:01.250 And I'm going to change just I'm just going to reduce a number of replicas to three. 02:02.210 --> 02:02.380 Okay. 02:02.420 --> 02:04.040 So let's go back to our terminal. 02:04.070 --> 02:09.770 And if we check the route of our project directory, we see the new directory that we created called 02:09.770 --> 02:10.370 DEPLOYMENT'S. 02:10.430 --> 02:17.960 And I'm going to create this deployment using the Cuttle Create Command along with the Dash F deployment 02:18.180 --> 02:19.280 and YAML file. 02:20.030 --> 02:23.020 And as you can see, the deployment has been created. 02:25.700 --> 02:28.430 So let's run the Cuttle Get Deployment's command. 02:31.350 --> 02:37.620 And I can see that we have one deployment which is created and it has three out of three ready parts 02:37.760 --> 02:39.810 and available hard three as well. 02:40.290 --> 02:45.500 So if you want to check the pod, we can run the you've to get parts command. 02:45.500 --> 02:51.360 And I can see that we have three pods which are in the running state, which were created a few moments 02:51.360 --> 02:51.750 ago. 02:54.850 --> 02:58.550 Now, let us run a cube, Carol, describe deployment. 02:58.590 --> 03:03.060 Command and the name of the deployment is my ab dash deployment. 03:04.470 --> 03:07.800 And here we can see a lot of similar information. 03:08.640 --> 03:12.540 So the name of the pod, the label of the deployment itself. 03:14.280 --> 03:18.000 And the the front end label that we set. 03:19.360 --> 03:25.200 And we see the selector that we use the same as that of the replica set, which is equal to my app. 03:26.010 --> 03:30.780 And it has three desired and three available parts which are in the running state. 03:31.470 --> 03:33.660 And here's the pod section. 03:34.430 --> 03:36.330 And the label of the part is my app. 03:36.350 --> 03:41.190 And here's the container details with the image said to Engine X. 03:42.120 --> 03:48.660 If you scroll to the bottom, you'll see that it also has an event section and it just shows the deployment 03:48.690 --> 03:57.030 controller and message, which is that the replica set for this deployment has been scaled to three. 03:58.270 --> 04:05.040 And now before we move on, let's run the cube to get all command, which shows all the objects we just 04:05.040 --> 04:06.090 created in the cluster. 04:06.180 --> 04:10.410 So you can see that we have one deployment, which is the deployment that we created. 04:10.530 --> 04:14.580 And there is a replica set which is created for that specific deployment. 04:15.660 --> 04:17.910 Called my app Dash Replica Set. 04:18.510 --> 04:22.620 And then we have the three pods which have been created using the pad replicas. 04:23.680 --> 04:25.530 OK, well, that's it for now. 04:25.950 --> 04:28.830 Head over to the labs and try this out for yourselves.