No.
Let's quickly go back again inside of the Kubernetes mini cube node and list again Docker containers,
and we will find out that now there is one more container which was created in the engine export.
So using up arrow I could go back to the Sage Command which I entered before.
Here it is and connect to this node again.
Enter DC user password and let's enter.
Here are Docker PS but now let's filter output by name engine and now I'll find out that there are two
different containers here with first one and Hero's second one which are related to engine x.
Here is name of the first container K eight as Engine X and Jennings default and so on.
And also there is one more container k8s Port and Jennings default and so on.
And this second container is called POS container here you see that inside of the container pause executable
was actually launched when container was created.
And if Docker is container runtime in Kubernetes, there are always such post containers which are created
for each specific port and such POS containers are created in order to, let's say, log namespace of
specific port.
And we discussed before that all containers inside of the same port actually share namespaces.
And this container, which is actually running our engine web server could be stopped, could be recreated
by Kubernetes, but port remains untouched.
And this second container, which is called post container, is required to keep namespace of the port.
All right.
That's how containers look right now.
And let's actually connect to this container where we are running engine service.
In order to connect to container, you could use either ID, this one or this name.
Let's connect to container.
By this ID, please select this container, not POS container and let's enter command docker exec dash
it.
Here is ID of the container and let's connect this container using SHA executable.
Now I am inside of the container.
Let's check its hostname and Jennings.
It is name of the port actually and the same name was assigned to this container.
And let's also check IP address of this container.
Here is such IP address 170 217 zero three and that's that IP address which we saw in the details of
the port.
Now let's try to connect to web server, which is running inside of this container where we are currently
in by using this IP address.
And for that we could utilize see URL command and here are paste IP address of this particular container
that we are inside of the container.
Let's try to make connection and here I see.
Welcome to again s page which was returned by this web server.
It means that again its web server is up and running.
Let's go out of this container.
And now we are still inside of the Kubernetes node that we made as a connection to it.
And now let's exit from this connection as well like that.
And now let's enter following command.
You still get ports this all wide and with such option you'll find also IP address of particular port
in this output.
And here is the same IP address which we just saw inside of the container.
Let's now try to connect to such IP address from our computer.
Our computer is external relative to our Kubernetes cluster because Kubernetes node is running inside
of the virtual machine.
And this IP address was assigned by Docker to particular container inside of the node.
Let's try to connect to such IP address.
I could utilize the same command SEO URL.
Here it is available on Mac.
Or you could simply open up web browser and connect to this IP address and you'll find out that you
will not be able to connect to engine container like that.
Because as I told you before, such IP address is internal IP address of the port and you are not able
to connect to such port from outside world outside of the classroom.
Great.
That's how we created very first port in our Kubernetes cluster.
And we also explored details of such port.
And I hope that now it is clear to you what happens when you create a port inside of the port.
Kubernetes creates container, and in order to create container, it has to pull image from the Docker
hub.
And in our example, Engine X image was pulled and new container was created based on that image.
Also, we went inside of the container and verified that engine, its web server is now actually running,
but we are not able to connect to such port from the outside because now it has only internal IP address
which was assigned by the Docker.
But of course creation of the port using cube ctrl run command is not really convenient because you
are not able to scale and for example, increase quantity of the ports.
There was just a single port which we created using Cube City Run Command.
That's why now let's simply delete created port so that there is command cube.
Still delete next will be name of the resource we would like to delete and it is port and here we'll
be name of the port in our example again because we specified such name for the port manually when we
entered Cube, it'll run command, so let's go ahead and delete such a port.
But again, it's deleted.
Q Still get polls and there are no resources found in the vault namespace and such port is simply gone.
And all volumes, all namespaces related to this particular port were removed.