In this demo, we're going to deploy a pod in our mini cube cluster.
As we discussed, a part is a most basic and the smallest unit in CORONETS.
So we will use the cube coral command line utility to interact with the coronets cluster.
Now, if you followed our demo earlier of deploying a cluster using mini cube, then you already have
the cube coral command line utility configured to work with the cluster.
We will run the command cube Cuttle run engine X, which is the name of the pod dash dash.
Image equals two engine X.
Now here is where we specify the docker image to be used.
While the port name could be anything, the image name has to be the name of an image available at Docker
Hub or any other container registry.
You can additionally specify a tag for the image name or a different address to an image hosted on another
registry.
If the image is hosted in a place that's other than Docker Hub.
Okay, so once we run this command, we see a port by the name and Genex has been created.
And you can check the status using the Cube Cuttle Get Parts Command.
Now here you can see the column name, which is an gen.
The status is running and we see that the there is a ready column which shows the number of containers
in a ready state.
We also see if the container has restarted since it was created.
And how long has the port been running?
We can get more information related to the pod by running the cube Carol.
Describe pod in Gen X Command.
And you'll notice that this provides a lot more information as compared to the get command.
So, for example, the name of the pod is in Gen X.
It shows any labels that has been assigned to this pod.
So this was created by default when we ran the run command.
It shows when it was started.
It chose the node that is that it is assigned to along with the IP address of the node.
So in this case, we just have a single node cluster set up using mini tube.
And the node name is Minnie Cube, and that is the IP address of this worker node.
Secondly, it also shows the IP address of the pod itself.
So in this case, the pod is assigned an IP of 172.
The 16 that zero dark three will cover more about the IP addresses of the pod.
Later in the networking section.
Now, moving on, we can see that it displays information related to the container.
So we know that there is a single container which uses the image in Genex.
If there were multiple containers, we would list them here.
I'll explain about creating a pod with multiple containers in the upcoming lectures.
But here we can also see that the ending next image was pulled from Docker Hub.
And if you scroll all the way to the bottom, you'll see additional information called events.
And here you see the list of events that occurred since the pod was created.
It went through multiple stages before it started.
We can see that the pod was assigned to the mini cube node.
If there were multiple nodes, you would see which node the pod was assigned to here.
And then it entered the pulling phase where the engine X image was pulled down from Docker Hub successfully.
And then the container called Engine X was created and started.
Now there is one other command that we can use to check the status of the port, and that is the same
commanders before that cubicle will get pod command.
But with the dash wide option and this provides additional information such as the node where the pod
is running and the IP address of the pod as well.
So this is the internal IP address of the party itself.
So each pod gets an internal IP of its own within the within the Cuban its cluster.
But more on that later.
That was a quick demonstration on how to run a pod in many KUB environment in the upcoming videos.
We will see how to create a pod using a Yamal definition file.