And now let's go ahead and create Kubernetes cluster.
For that, please utilize command mini cube start.
But first, let's enter mini cube status in order to check current status of the cluster.
Mini cube status here I see that profile mini cube not found run mini cube profile this to you all profiles
and also I see that in order to start cluster I have to run mini cube, start command.
That's what we are about to do right now.
Let's create cluster meaning you start and here I would like to ask you to start mini cube cluster with
option and this option will be driver and you should write it with two dashes.
There's dash driver and here we'll be equal sign.
And after it you have to specify virtual machine or container manager, which you would utilize in order
to create mini cube cluster.
I mentioned before that if your Windows user, I recommend to you to use Hyper-V.
Therefore if you are on windows, simply enter here Hyper-V like that all lowercase without dash does
this driver equals sign Hyper-V.
If you are a macOS user, you could go ahead with any of those options.
VirtualBox Parallels or VMware Fusion.
I will utilize VirtualBox.
If you don't have your toolbox, please go ahead and install it.
Enter here below toolbox and click on the first link here.
Your toolbox is free.
And here was a link where you could download VirtualBox.
So if you don't have your toolbox and if you are a macOS user, please go ahead and download your toolbox.
Great.
I already have your toolbox installed.
That's why I will simply specify it as a value for the driver option here.
So I'll type the toll box.
Let's go ahead and create mini cube cluster inside of the virtual box.
Virtual machine, in my case, creating virtual box, virtual machine, quantity of CPUs, memory and
disk.
It will take a while.
Let me wait a bit.
Virtual machine was created and now I see message preparing Kubernetes on Docker and it means that by
default we will utilize Docker container runtime for running actual containers inside of the Kubernetes
cluster.
Here I see step generating certificates and keys, booting up control plane.
And finally at the end I see done.
The deal is now configured to use mini cube cluster and that means that you don't need to do anything
in order to connect from cube skittle to actual mini cube cluster.
This connection was created automatically for you during the creation of the mini cube cluster.
Also, in my case, I see such a warning.
You have selected VirtualBox driver, but there are better options for better performance and support.
Consider using a different driver, HyperCard Parallels or VMware.
Now let's actually verify status of this Kubernetes cluster.
And for that you could enter command mini cube status.
And you should find out that host is running Kubernetes running API server is running and cube config
is configured.
That's normal status of the mini cube cluster.
And now we are actually able to create deployment services at etc. inside of this mini cube cluster.
Also, I would like to mention that I don't have Docker running right now.
I actually have it installed on this computer, but over here in the Icons Bar, I don't see Docker
icon.
It means that now Kubernetes on my local computer does not utilize actual Docker installation on my
computer.
But there is Docker which is running inside of the mini cube node, and that's what we will check right
now.