Great.
Now let's try to connect to one of the ports, for instance, this one.
Let's grab its IP address.
And before we already tried to connect to one of the ports from our local computer and again, our local
computer is external relative to Kubernetes cluster.
It is very, very important.
Let's try to connect to this IP address, see URL and paste.
IP address and connection is not successful.
Let's now go inside of the node mini cube node and try to connect to this port, any of those ports
from inside of the node.
And it will mean that we are trying to connect to the port inside of the cluster.
Let's S-H again to our mini cube node as a sage docker add and this IP address.
In your case, the sap is of course different.
Password is TSI user.
And now here, let's see your URL and enter IP address of one of the ports.
Any port works here.
So let's see your URL.
And I was able to connect to specific port by its IP address.
Let's try to connect to another port with another IP.
For instance, let's try 0.3.
I'm not sure whether I have such port running.
Yes, I have.
And I also got response from such port with such IP address that now I'm located inside of the node
and I am able to connect to ports which are running on this specific node using IP addresses of those
ports.
Let's exit from this node and again, let's list ports along with IP addresses.
So I was able to connect to this port and this port from the node.
But of course such IP addresses are assigned to both dynamically when new posts are created and you
should not rely on IP addresses of the ports if you would like to connect to a specific port.
Therefore, it's not convenient to utilize such IP addresses and you should utilize some sort of other
IP addresses which are managed by Kubernetes and which allow you to connect to any of the ports inside
of the deployment.