WEBVTT 00:00.170 --> 00:04.320 In this demo, we're going to deploy a pod in our mini cube cluster. 00:04.800 --> 00:09.220 As we discussed, a part is a most basic and the smallest unit in CORONETS. 00:09.750 --> 00:14.640 So we will use the cube coral command line utility to interact with the coronets cluster. 00:15.360 --> 00:20.670 Now, if you followed our demo earlier of deploying a cluster using mini cube, then you already have 00:20.700 --> 00:24.810 the cube coral command line utility configured to work with the cluster. 00:25.410 --> 00:32.010 We will run the command cube Cuttle run engine X, which is the name of the pod dash dash. 00:32.100 --> 00:35.430 Image equals two engine X. 00:36.240 --> 00:40.350 Now here is where we specify the docker image to be used. 00:41.130 --> 00:47.760 While the port name could be anything, the image name has to be the name of an image available at Docker 00:47.760 --> 00:50.670 Hub or any other container registry. 00:51.360 --> 00:59.220 You can additionally specify a tag for the image name or a different address to an image hosted on another 00:59.220 --> 00:59.910 registry. 01:00.390 --> 01:05.880 If the image is hosted in a place that's other than Docker Hub. 01:06.560 --> 01:13.560 Okay, so once we run this command, we see a port by the name and Genex has been created. 01:14.010 --> 01:17.540 And you can check the status using the Cube Cuttle Get Parts Command. 01:18.100 --> 01:20.610 Now here you can see the column name, which is an gen. 01:21.150 --> 01:27.240 The status is running and we see that the there is a ready column which shows the number of containers 01:27.330 --> 01:28.260 in a ready state. 01:28.950 --> 01:32.340 We also see if the container has restarted since it was created. 01:32.490 --> 01:34.590 And how long has the port been running? 01:35.160 --> 01:39.520 We can get more information related to the pod by running the cube Carol. 01:39.660 --> 01:41.910 Describe pod in Gen X Command. 01:42.900 --> 01:48.150 And you'll notice that this provides a lot more information as compared to the get command. 01:48.300 --> 01:51.480 So, for example, the name of the pod is in Gen X. 01:52.050 --> 01:55.350 It shows any labels that has been assigned to this pod. 01:55.800 --> 01:59.400 So this was created by default when we ran the run command. 02:01.770 --> 02:03.120 It shows when it was started. 02:03.450 --> 02:08.850 It chose the node that is that it is assigned to along with the IP address of the node. 02:09.450 --> 02:12.960 So in this case, we just have a single node cluster set up using mini tube. 02:13.260 --> 02:17.700 And the node name is Minnie Cube, and that is the IP address of this worker node. 02:18.510 --> 02:21.960 Secondly, it also shows the IP address of the pod itself. 02:22.080 --> 02:26.150 So in this case, the pod is assigned an IP of 172. 02:26.160 --> 02:31.590 The 16 that zero dark three will cover more about the IP addresses of the pod. 02:31.980 --> 02:33.510 Later in the networking section. 02:34.370 --> 02:38.550 Now, moving on, we can see that it displays information related to the container. 02:38.580 --> 02:42.820 So we know that there is a single container which uses the image in Genex. 02:43.500 --> 02:47.010 If there were multiple containers, we would list them here. 02:47.730 --> 02:51.900 I'll explain about creating a pod with multiple containers in the upcoming lectures. 02:52.710 --> 02:58.920 But here we can also see that the ending next image was pulled from Docker Hub. 03:00.150 --> 03:05.010 And if you scroll all the way to the bottom, you'll see additional information called events. 03:05.460 --> 03:09.960 And here you see the list of events that occurred since the pod was created. 03:11.280 --> 03:13.740 It went through multiple stages before it started. 03:14.040 --> 03:17.370 We can see that the pod was assigned to the mini cube node. 03:18.000 --> 03:22.560 If there were multiple nodes, you would see which node the pod was assigned to here. 03:23.040 --> 03:30.330 And then it entered the pulling phase where the engine X image was pulled down from Docker Hub successfully. 03:30.930 --> 03:35.220 And then the container called Engine X was created and started. 03:36.030 --> 03:42.540 Now there is one other command that we can use to check the status of the port, and that is the same 03:42.540 --> 03:45.000 commanders before that cubicle will get pod command. 03:45.030 --> 03:52.410 But with the dash wide option and this provides additional information such as the node where the pod 03:52.410 --> 03:55.170 is running and the IP address of the pod as well. 03:55.560 --> 03:59.310 So this is the internal IP address of the party itself. 03:59.520 --> 04:04.470 So each pod gets an internal IP of its own within the within the Cuban its cluster. 04:05.670 --> 04:06.690 But more on that later. 04:07.350 --> 04:14.640 That was a quick demonstration on how to run a pod in many KUB environment in the upcoming videos. 04:14.700 --> 04:19.380 We will see how to create a pod using a Yamal definition file.