1
00:00:04,560 --> 00:00:08,189
And now let's go ahead and create Kubernetes cluster.

2
00:00:08,370 --> 00:00:12,360
For that, please utilize command mini cube start.

3
00:00:12,360 --> 00:00:17,940
But first, let's enter mini cube status in order to check current status of the cluster.

4
00:00:17,940 --> 00:00:24,840
Mini cube status here I see that profile mini cube not found run mini cube profile this to you all profiles

5
00:00:24,840 --> 00:00:30,300
and also I see that in order to start cluster I have to run mini cube, start command.

6
00:00:30,300 --> 00:00:33,060
That's what we are about to do right now.

7
00:00:33,360 --> 00:00:41,670
Let's create cluster meaning you start and here I would like to ask you to start mini cube cluster with

8
00:00:41,670 --> 00:00:47,010
option and this option will be driver and you should write it with two dashes.

9
00:00:47,010 --> 00:00:50,730
There's dash driver and here we'll be equal sign.

10
00:00:50,730 --> 00:00:57,270
And after it you have to specify virtual machine or container manager, which you would utilize in order

11
00:00:57,270 --> 00:00:59,160
to create mini cube cluster.

12
00:00:59,460 --> 00:01:05,610
I mentioned before that if your Windows user, I recommend to you to use Hyper-V.

13
00:01:05,700 --> 00:01:14,220
Therefore if you are on windows, simply enter here Hyper-V like that all lowercase without dash does

14
00:01:14,220 --> 00:01:16,830
this driver equals sign Hyper-V.

15
00:01:17,940 --> 00:01:21,810
If you are a macOS user, you could go ahead with any of those options.

16
00:01:21,810 --> 00:01:24,720
VirtualBox Parallels or VMware Fusion.

17
00:01:25,110 --> 00:01:27,510
I will utilize VirtualBox.

18
00:01:27,570 --> 00:01:31,320
If you don't have your toolbox, please go ahead and install it.

19
00:01:31,650 --> 00:01:36,990
Enter here below toolbox and click on the first link here.

20
00:01:39,760 --> 00:01:41,500
Your toolbox is free.

21
00:01:41,500 --> 00:01:45,310
And here was a link where you could download VirtualBox.

22
00:01:45,430 --> 00:01:51,910
So if you don't have your toolbox and if you are a macOS user, please go ahead and download your toolbox.

23
00:01:53,160 --> 00:01:53,730
Great.

24
00:01:53,760 --> 00:01:56,150
I already have your toolbox installed.

25
00:01:56,160 --> 00:02:01,980
That's why I will simply specify it as a value for the driver option here.

26
00:02:02,040 --> 00:02:05,430
So I'll type the toll box.

27
00:02:06,060 --> 00:02:10,530
Let's go ahead and create mini cube cluster inside of the virtual box.

28
00:02:10,560 --> 00:02:17,880
Virtual machine, in my case, creating virtual box, virtual machine, quantity of CPUs, memory and

29
00:02:17,880 --> 00:02:18,540
disk.

30
00:02:18,780 --> 00:02:20,250
It will take a while.

31
00:02:20,250 --> 00:02:21,450
Let me wait a bit.

32
00:02:21,600 --> 00:02:28,560
Virtual machine was created and now I see message preparing Kubernetes on Docker and it means that by

33
00:02:28,560 --> 00:02:35,640
default we will utilize Docker container runtime for running actual containers inside of the Kubernetes

34
00:02:35,640 --> 00:02:36,390
cluster.

35
00:02:36,930 --> 00:02:42,840
Here I see step generating certificates and keys, booting up control plane.

36
00:02:44,230 --> 00:02:46,550
And finally at the end I see done.

37
00:02:46,960 --> 00:02:52,990
The deal is now configured to use mini cube cluster and that means that you don't need to do anything

38
00:02:52,990 --> 00:02:57,920
in order to connect from cube skittle to actual mini cube cluster.

39
00:02:57,940 --> 00:03:03,100
This connection was created automatically for you during the creation of the mini cube cluster.

40
00:03:03,250 --> 00:03:06,810
Also, in my case, I see such a warning.

41
00:03:06,820 --> 00:03:12,460
You have selected VirtualBox driver, but there are better options for better performance and support.

42
00:03:12,460 --> 00:03:16,750
Consider using a different driver, HyperCard Parallels or VMware.

43
00:03:16,990 --> 00:03:21,550
Now let's actually verify status of this Kubernetes cluster.

44
00:03:21,550 --> 00:03:25,120
And for that you could enter command mini cube status.

45
00:03:26,280 --> 00:03:33,000
And you should find out that host is running Kubernetes running API server is running and cube config

46
00:03:33,000 --> 00:03:34,080
is configured.

47
00:03:34,560 --> 00:03:37,860
That's normal status of the mini cube cluster.

48
00:03:37,860 --> 00:03:45,630
And now we are actually able to create deployment services at etc. inside of this mini cube cluster.

49
00:03:46,050 --> 00:03:50,410
Also, I would like to mention that I don't have Docker running right now.

50
00:03:50,430 --> 00:03:56,970
I actually have it installed on this computer, but over here in the Icons Bar, I don't see Docker

51
00:03:56,970 --> 00:03:57,440
icon.

52
00:03:57,450 --> 00:04:05,160
It means that now Kubernetes on my local computer does not utilize actual Docker installation on my

53
00:04:05,160 --> 00:04:05,940
computer.

54
00:04:06,060 --> 00:04:14,010
But there is Docker which is running inside of the mini cube node, and that's what we will check right

55
00:04:14,010 --> 00:04:14,520
now.

