1
00:00:04,200 --> 00:00:10,720
As you all know, each node in the Kubernetes cluster is just server, either virtual or physical.

2
00:00:10,740 --> 00:00:18,180
In our case, we have created a virtual server and you could connect to any server by using SSH protocol.

3
00:00:18,180 --> 00:00:26,070
And in order to connect via Sage, we first need to find out which IP address was assigned to Kubernetes.

4
00:00:26,100 --> 00:00:29,640
Node Mini Cube provides command for that.

5
00:00:29,790 --> 00:00:38,520
Simply type in cube IP and you'll see which IP address was assigned to a virtual machine which is running

6
00:00:38,520 --> 00:00:42,120
our Kubernetes node, which was created by mini cube.

7
00:00:42,120 --> 00:00:43,290
Here was IP address.

8
00:00:43,290 --> 00:00:49,920
In my case, simply grab this IP address and afterwards type as a sage docker.

9
00:00:49,950 --> 00:00:58,710
It is username which is default username for such a node, such virtual server and after at sign based

10
00:00:58,710 --> 00:01:02,850
IP address of mini cube node and after.

11
00:01:03,120 --> 00:01:04,470
Please press enter.

12
00:01:10,820 --> 00:01:13,160
You will be presented with fingerprint.

13
00:01:13,190 --> 00:01:15,250
Please go ahead and type here.

14
00:01:15,260 --> 00:01:17,690
Yes, we trust such a fingerprint.

15
00:01:17,810 --> 00:01:21,290
And afterwards you will be prompted for password.

16
00:01:21,320 --> 00:01:23,620
Default password for mini cube.

17
00:01:23,660 --> 00:01:26,630
Virtual machine is DC user.

18
00:01:26,870 --> 00:01:29,320
Please go ahead and type it here.

19
00:01:29,330 --> 00:01:33,230
So username is docker and password is DC user.

20
00:01:33,860 --> 00:01:36,260
Password was entered and now I see.

21
00:01:36,260 --> 00:01:38,930
Welcome prompt from the mini cube server.

22
00:01:38,960 --> 00:01:47,060
Now I am inside of the Kubernetes node and first command, which I would like to ask you to enter.

23
00:01:47,060 --> 00:01:48,460
Here is Docker.

24
00:01:48,550 --> 00:01:56,840
PS Such command will list you all running docker containers and here are a bunch of different containers

25
00:01:56,840 --> 00:02:00,560
which were created inside of the Kubernetes node.

26
00:02:00,920 --> 00:02:07,550
And again, please recap that Docker is default container runtime for Kubernetes.

27
00:02:07,670 --> 00:02:15,260
There are other container runtimes such as cry o and container d, but here we see that there are bunch

28
00:02:15,260 --> 00:02:20,450
of different containers which were created by Docker inside of the mini cube node.

29
00:02:21,050 --> 00:02:28,550
And for instance here I see such container as cube API, server, cube scheduler and so on.

30
00:02:28,670 --> 00:02:35,240
Recap that we discussed with you different services which are running on master nodes and worker nodes,

31
00:02:35,240 --> 00:02:41,930
and those services are actually running inside of the containers as you see right now here.

32
00:02:42,230 --> 00:02:50,150
Also there are such containers as the cube proxy storage provision or for instance, core DNS.

33
00:02:50,360 --> 00:02:54,050
And again, every container has its own purpose.

34
00:02:55,070 --> 00:03:00,600
That's how you could verify which containers were created inside of the Kubernetes node.

35
00:03:00,620 --> 00:03:08,030
But if I enter here Cube Ctrl command, I'll see error cube CTL Command not found because Cube City

36
00:03:08,030 --> 00:03:11,990
L Command is not available inside of the Kubernetes node.

37
00:03:12,200 --> 00:03:17,240
Cube still is external tool, which is used in order to manage Kubernetes cluster.

38
00:03:17,330 --> 00:03:21,140
That's why let's now go out of this SSH connection.

39
00:03:21,140 --> 00:03:25,700
Connection was closed and now let's utilize cube style command here.

40
00:03:25,730 --> 00:03:32,240
Of course, Cube still is available locally on our computers because we have installed Cube still before.

41
00:03:32,630 --> 00:03:37,070
Let's first check cluster info, cube, CTL cluster.

42
00:03:37,100 --> 00:03:40,520
That's info and I get follwing output.

43
00:03:40,580 --> 00:03:47,630
Kubernetes control plane is running and here I see IP address which we just saw after entering mini

44
00:03:47,630 --> 00:03:48,930
cube IP command.

45
00:03:48,950 --> 00:03:52,940
In your case, of course, such IP address will be different.

46
00:03:53,210 --> 00:03:57,500
And also I see that core DNS service is running as well.

47
00:03:58,310 --> 00:04:06,860
It means that now we are able actually to create deployments, services and etc. on our Kubernetes cluster.

48
00:04:07,010 --> 00:04:12,190
But first, let's list nodes which are available in our Kubernetes cluster.

49
00:04:12,200 --> 00:04:16,459
For that, please enter command cube, CTL, get nodes.

50
00:04:17,480 --> 00:04:23,330
And here I see just a single node because mini cube creates single node cluster.

51
00:04:23,330 --> 00:04:31,760
Here is name of such node status is ready and here are roles control plane and master lookup that now

52
00:04:31,760 --> 00:04:33,980
inside of our mini cube cluster.

53
00:04:34,010 --> 00:04:40,220
This single node acts both as master node and worker node and on worker node.

54
00:04:40,250 --> 00:04:47,390
Kubernetes creates different ports related to your deployments, which you deploy in Kubernetes cluster.

55
00:04:47,690 --> 00:04:52,700
Now let me check which ports are available right now in this cluster.

56
00:04:52,700 --> 00:05:01,250
For that, let's enter command cube, CTL, get ports and now I see output no resources found in default

57
00:05:01,250 --> 00:05:02,420
namespace.

58
00:05:03,650 --> 00:05:09,710
Let's list all namespaces which are available now in this Kubernetes cluster.

59
00:05:09,710 --> 00:05:11,360
For that, please enter command cube.

60
00:05:11,450 --> 00:05:14,390
It'll get name spaces.

61
00:05:15,160 --> 00:05:15,930
Like that.

62
00:05:15,940 --> 00:05:21,550
And I see several namespaces like default cube node leaves.

63
00:05:21,580 --> 00:05:29,590
Cube public and cube system namespaces are used in Kubernetes in order to group different resources

64
00:05:29,590 --> 00:05:31,360
and configuration objects.

65
00:05:32,380 --> 00:05:40,090
And if you enter simply cube city get ports, you will see only ports available inside of the default

66
00:05:40,090 --> 00:05:41,680
namespace here.

67
00:05:42,250 --> 00:05:48,850
And by the way, all ports which will create throughout the scrolls will be created in default namespace,

68
00:05:48,850 --> 00:05:51,790
but we have not yet created any ports so far.

69
00:05:52,300 --> 00:05:53,020
That's why.

70
00:05:53,020 --> 00:05:58,990
Let's try to find out which ports are running inside of other namespaces.

71
00:05:58,990 --> 00:06:00,910
For instance, cube system.

72
00:06:01,240 --> 00:06:06,610
In order to list ports in specific namespace, you have to utilize namespace option.

73
00:06:06,610 --> 00:06:09,010
So Cube still get ports.

74
00:06:09,250 --> 00:06:15,220
There's there's namespace equals sign and here enter cube system.

75
00:06:15,460 --> 00:06:17,710
Let's go ahead and run this command.

76
00:06:17,710 --> 00:06:24,820
And now here in this namespace cube system, I see such ports as core DNS.

77
00:06:24,850 --> 00:06:32,800
It is CD which stores all logs of entire Kubernetes cluster cube API is server cube controller, cube,

78
00:06:32,800 --> 00:06:36,230
proxy cube scheduler and storage provisional.

79
00:06:36,310 --> 00:06:41,620
All those ports are system ports which are running on this master node.

80
00:06:43,340 --> 00:06:44,060
All right.

81
00:06:44,060 --> 00:06:49,580
That's how we could find out which ports are running right now in our Kubernetes cluster.