As you all know, each node in the Kubernetes cluster is just server, either virtual or physical.
In our case, we have created a virtual server and you could connect to any server by using SSH protocol.
And in order to connect via Sage, we first need to find out which IP address was assigned to Kubernetes.
Node Mini Cube provides command for that.
Simply type in cube IP and you'll see which IP address was assigned to a virtual machine which is running
our Kubernetes node, which was created by mini cube.
Here was IP address.
In my case, simply grab this IP address and afterwards type as a sage docker.
It is username which is default username for such a node, such virtual server and after at sign based
IP address of mini cube node and after.
Please press enter.
You will be presented with fingerprint.
Please go ahead and type here.
Yes, we trust such a fingerprint.
And afterwards you will be prompted for password.
Default password for mini cube.
Virtual machine is DC user.
Please go ahead and type it here.
So username is docker and password is DC user.
Password was entered and now I see.
Welcome prompt from the mini cube server.
Now I am inside of the Kubernetes node and first command, which I would like to ask you to enter.
Here is Docker.
PS Such command will list you all running docker containers and here are a bunch of different containers
which were created inside of the Kubernetes node.
And again, please recap that Docker is default container runtime for Kubernetes.
There are other container runtimes such as cry o and container d, but here we see that there are bunch
of different containers which were created by Docker inside of the mini cube node.
And for instance here I see such container as cube API, server, cube scheduler and so on.
Recap that we discussed with you different services which are running on master nodes and worker nodes,
and those services are actually running inside of the containers as you see right now here.
Also there are such containers as the cube proxy storage provision or for instance, core DNS.
And again, every container has its own purpose.
That's how you could verify which containers were created inside of the Kubernetes node.
But if I enter here Cube Ctrl command, I'll see error cube CTL Command not found because Cube City
L Command is not available inside of the Kubernetes node.
Cube still is external tool, which is used in order to manage Kubernetes cluster.
That's why let's now go out of this SSH connection.
Connection was closed and now let's utilize cube style command here.
Of course, Cube still is available locally on our computers because we have installed Cube still before.
Let's first check cluster info, cube, CTL cluster.
That's info and I get follwing output.
Kubernetes control plane is running and here I see IP address which we just saw after entering mini
cube IP command.
In your case, of course, such IP address will be different.
And also I see that core DNS service is running as well.
It means that now we are able actually to create deployments, services and etc. on our Kubernetes cluster.
But first, let's list nodes which are available in our Kubernetes cluster.
For that, please enter command cube, CTL, get nodes.
And here I see just a single node because mini cube creates single node cluster.
Here is name of such node status is ready and here are roles control plane and master lookup that now
inside of our mini cube cluster.
This single node acts both as master node and worker node and on worker node.
Kubernetes creates different ports related to your deployments, which you deploy in Kubernetes cluster.
Now let me check which ports are available right now in this cluster.
For that, let's enter command cube, CTL, get ports and now I see output no resources found in default
namespace.
Let's list all namespaces which are available now in this Kubernetes cluster.
For that, please enter command cube.
It'll get name spaces.
Like that.
And I see several namespaces like default cube node leaves.
Cube public and cube system namespaces are used in Kubernetes in order to group different resources
and configuration objects.
And if you enter simply cube city get ports, you will see only ports available inside of the default
namespace here.
And by the way, all ports which will create throughout the scrolls will be created in default namespace,
but we have not yet created any ports so far.
That's why.
Let's try to find out which ports are running inside of other namespaces.
For instance, cube system.
In order to list ports in specific namespace, you have to utilize namespace option.
So Cube still get ports.
There's there's namespace equals sign and here enter cube system.
Let's go ahead and run this command.
And now here in this namespace cube system, I see such ports as core DNS.
It is CD which stores all logs of entire Kubernetes cluster cube API is server cube controller, cube,
proxy cube scheduler and storage provisional.
All those ports are system ports which are running on this master node.
All right.
That's how we could find out which ports are running right now in our Kubernetes cluster.