1

00:00:00,290 --> 00:00:05,970

In this lecture, we will look at the cube admin tool, which can be used to bootstrap a corporate net



2

00:00:05,970 --> 00:00:12,780

as cluster, the cube admin tool helps us set up a multi node cluster following the cabinet as best



3

00:00:12,780 --> 00:00:13,470

practices.



4

00:00:14,490 --> 00:00:20,400

As we discussed, the Cuban netas cluster consists of various components, such as the Cuba API server,



5

00:00:20,520 --> 00:00:26,910

LCD controllers, etc., and we've seen some of the requirements are on security and certificates to



6

00:00:26,910 --> 00:00:33,300

enable communication between these components, installing all of these various components individually



7

00:00:33,330 --> 00:00:39,450

on different nodes and modifying the configuration files to make sure these components point to each



8

00:00:39,450 --> 00:00:39,750

other.



9

00:00:40,050 --> 00:00:44,070

And setting up certificates to make it work is a tedious task.



10

00:00:44,850 --> 00:00:49,590

The cube admin tool helps us by taking care of all of those tasks.



11

00:00:50,600 --> 00:00:56,330

Let's go through the steps to set up a cabinet, this cluster using the cube admin tool at a high level.



12

00:00:57,420 --> 00:01:03,090

First, you must have multiple systems or virtual machines provisioned for configuring a cluster.



13

00:01:03,630 --> 00:01:07,140

We will see how to set up your laptop to do just that.



14

00:01:07,860 --> 00:01:09,060

That's if you're not familiar with it.



15

00:01:09,450 --> 00:01:15,180

Once the systems are created, designate one node as master and others as worker notes.



16

00:01:15,690 --> 00:01:19,200

The next step is to install a container runtime on the hosts.



17

00:01:19,470 --> 00:01:20,730

We will be using Docker.



18

00:01:21,030 --> 00:01:23,730

So we must install Docker on all the notes.



19

00:01:24,730 --> 00:01:31,570

The next step is to install Kube admin tool on all the notes, the cube admin tool helps us bootstrap



20

00:01:31,570 --> 00:01:36,880

the carbonated solution by installing and configuring all the required components in the right nodes



21

00:01:36,910 --> 00:01:37,750

in the right order.



22

00:01:39,010 --> 00:01:43,690

The next step is to initialize the master server during this process.



23

00:01:44,020 --> 00:01:48,430

All the required components are installed and configured on the master server.



24

00:01:49,630 --> 00:01:55,900

Once the master is initialized and before joining the worker notes to the master, you must ensure that



25

00:01:55,900 --> 00:02:02,470

the network prerequisites are met and normal network connectivity between the systems is not sufficient



26

00:02:02,470 --> 00:02:03,830

for this Cooperton.



27

00:02:03,920 --> 00:02:09,370

This requires a special networking solution between the master and worker notes, which is called as



28

00:02:09,370 --> 00:02:10,600

the pod network.



29

00:02:11,790 --> 00:02:14,040

The last step is to join the worker.



30

00:02:14,060 --> 00:02:15,330

Note to the master note.



31

00:02:15,910 --> 00:02:20,160

Well, then all set to launch our application in the cabinet as environment.



32

00:02:21,240 --> 00:02:27,390

We will now see a demo of setting up cabernets using the cube admin tool in our local environment.