1
00:00:04,440 --> 00:00:07,680
Now let's go ahead and create a board manually.

2
00:00:07,680 --> 00:00:12,330
And for that we could utilize command, which is similar to Docker run command.

3
00:00:12,330 --> 00:00:17,340
But with Docker Run Command, you could create just a single Docker container here.

4
00:00:17,340 --> 00:00:23,010
You could utilize Cube still run command in order to create just a single port.

5
00:00:23,100 --> 00:00:24,510
Let's do that cube.

6
00:00:24,720 --> 00:00:27,480
It'll run here will be named.

7
00:00:27,600 --> 00:00:32,790
Let's for instance utilize engine x docker image which is available at Docker Hub.

8
00:00:32,790 --> 00:00:40,680
For that let's enter here name of the port engine x and afterwards let's add option image and this value

9
00:00:40,710 --> 00:00:42,210
will be in Genesis.

10
00:00:42,300 --> 00:00:50,730
And Genesis here is name of the Docker image which will be pulled automatically and new container will

11
00:00:50,730 --> 00:00:57,000
be created based on this image and this container will be running inside of the Kubernetes port.

12
00:00:57,990 --> 00:01:00,540
Let's go ahead and see what will happen.

13
00:01:01,200 --> 00:01:02,280
It'll run again.

14
00:01:02,280 --> 00:01:09,060
X does this image equals sign and genesis and here I see output port and Genesis created.

15
00:01:09,090 --> 00:01:10,500
Let's enter command cube.

16
00:01:10,620 --> 00:01:18,000
It'll get ports and here I see now single port and Genesis.

17
00:01:18,060 --> 00:01:25,920
It is not yet ready and its status is container creating Let's enter same command again you still get

18
00:01:25,920 --> 00:01:29,040
ports and now I see that this port is now run.

19
00:01:29,070 --> 00:01:31,800
It is ready and its status is run.

20
00:01:32,640 --> 00:01:39,140
Of course it took some time in order to create such a port because inside of it there was engine is

21
00:01:39,150 --> 00:01:48,600
container and docker inside of the Kubernetes node was actually requested to pull engine x image from

22
00:01:48,600 --> 00:01:54,510
Docker Hub and create corresponding container based on such image and Genesis.

23
00:01:55,050 --> 00:02:00,510
Let's now find out details of this specific port with name and Genesis.

24
00:02:00,510 --> 00:02:03,390
This name, we specify it manually here.

25
00:02:03,720 --> 00:02:05,910
For that, please enter command cube.

26
00:02:05,940 --> 00:02:13,050
Still describe port and here we'll be name of the port which you would like to describe.

27
00:02:13,050 --> 00:02:15,420
Get details about here.

28
00:02:15,420 --> 00:02:16,410
We'll be in Genesis.

29
00:02:16,410 --> 00:02:23,310
It is name of the running port and here are many different details related to this specific port.

30
00:02:23,310 --> 00:02:32,760
Let me scroll a bit up and here I'll find out such information as a namespace this port belongs to and

31
00:02:32,760 --> 00:02:36,360
it was automatically assigned to default namespace.

32
00:02:36,360 --> 00:02:41,820
That's why we were able to see it in the list when we entered command cubes.

33
00:02:41,850 --> 00:02:48,120
It'll get port because such command lists all ports inside of the default namespace.

34
00:02:49,020 --> 00:02:56,760
Here is information about node where such specific port was created or kept that Kubernetes automatically

35
00:02:56,760 --> 00:03:04,470
distributes load across all nodes work and nodes inside of the cluster, and it selects specific node

36
00:03:04,470 --> 00:03:06,030
for specific port.

37
00:03:06,480 --> 00:03:11,010
And that's information about the node where this particular port was created.

38
00:03:11,010 --> 00:03:18,090
In our single node cluster, of course, you will see the same node each time when you create any port

39
00:03:18,090 --> 00:03:20,520
and here is IP address of such node.

40
00:03:20,730 --> 00:03:28,470
Here is start time here all labels status is running and here is IP address which was assigned to this

41
00:03:28,470 --> 00:03:37,830
particular port 170 217 zero three But please note that now we will not be able to connect to this particular

42
00:03:37,830 --> 00:03:41,460
port using such internal IP address of the port.

43
00:03:41,760 --> 00:03:47,610
In order to be able to connect to ports, you have to create services in Kubernetes, and that's what

44
00:03:47,610 --> 00:03:50,610
we will look at a bit later here.

45
00:03:50,610 --> 00:03:56,250
Below, you could also find out which containers were created inside of this port.

46
00:03:56,250 --> 00:03:58,560
And there was just a single container.

47
00:03:58,560 --> 00:04:01,290
Here is ID of such container.

48
00:04:01,320 --> 00:04:08,610
Here was long ID here was image which was utilized for this particular container and that's that image

49
00:04:08,610 --> 00:04:14,040
which we specified using this dash image option when we created new port.

50
00:04:14,340 --> 00:04:21,540
Here is image ID and it is ID of the image from the Docker hub because by default, Kubernetes pulls

51
00:04:21,540 --> 00:04:23,460
all images from the Docker hub.

52
00:04:23,460 --> 00:04:29,880
Of course, it's possible to configure Kubernetes to pull images from other repository hosting services,

53
00:04:29,880 --> 00:04:32,160
but default is Docker hub.

54
00:04:32,640 --> 00:04:33,210
All right.

55
00:04:33,210 --> 00:04:36,870
This are details about this particular port.

56
00:04:37,170 --> 00:04:41,340
And we find out that there was IP address assigned to this board.

57
00:04:41,370 --> 00:04:44,910
There was a container which was created inside of this port.

58
00:04:44,910 --> 00:04:50,340
And here are logs related to creation of this particular port.

59
00:04:50,790 --> 00:04:57,270
You see that this particular port was successfully assigned to mini cube node here with message about

60
00:04:57,270 --> 00:04:59,790
pulling image and Jennings from the Docker hub.

61
00:05:00,170 --> 00:05:07,840
Successfully pooled image, created container engineers and started container and Genesis.

62
00:05:07,850 --> 00:05:13,070
And it means that now there is engine is container running inside of the created port.

63
00:05:13,310 --> 00:05:19,610
Again, you could find the list of all ports by entering command cube CTL get ports.

64
00:05:19,970 --> 00:05:24,980
And here was a single port available right now in the default namespace.

