WEBVTT 00:01.050 --> 00:04.680 We have now set up the notes required to set up a Cuban natus cluster. 00:05.230 --> 00:09.150 We have set up a master node and two worker nodes, node zero one and not zero two. 00:10.080 --> 00:15.060 Let us now proceed to the Canadian documentation page to install a corporate netas cluster. 00:15.960 --> 00:17.700 We will start with the prerequisites. 00:18.180 --> 00:23.910 So we must have a supported operating system like, for example, open to sixteen point two or four 00:23.910 --> 00:26.190 or higher, which we already do. 00:26.430 --> 00:28.410 That's what we did in the previous demo. 00:28.920 --> 00:35.190 We have some hardware requirements to have at least two gibi of RAM to S.P. use and network connectivity 00:35.220 --> 00:39.630 between the rearms, which we have already taken care of in the previous video. 00:40.290 --> 00:46.320 Another thing is to make sure that our firewall and network security settings are in place. 00:46.650 --> 00:49.980 Otherwise, the nodes will run into connectivity issues. 00:52.340 --> 00:56.080 For this, we must let IP tables see breached traffic. 00:56.450 --> 01:02.060 We must first make sure the B r underscore net filter module is loaded before the step. 01:02.360 --> 01:05.630 So we can do that by running the command allez mode. 01:06.260 --> 01:09.050 Grep b r underscore net filter. 01:11.670 --> 01:14.930 So we see that it's not loaded as there is no result. 01:15.070 --> 01:19.300 So we run the more probe command to load the kernel module. 01:27.290 --> 01:29.420 We know execute that on all the notes. 01:43.570 --> 01:49.210 Once that is done, we run this set of commands to create the new COL parameters. 01:49.930 --> 01:51.760 We then do that on all the nodes. 02:11.050 --> 02:14.170 The next step is to install container runtime on the notes. 02:14.800 --> 02:18.520 We will be using Docker in this example for this. 02:18.550 --> 02:21.460 We use the documentation link and click on Docker. 02:22.480 --> 02:26.410 We will use these commands to install the latest table version of Docker. 02:27.250 --> 02:28.690 These neat route privileges. 02:29.120 --> 02:34.240 So I will switch to Suda to make the next steps easier by running the Suda dash. 02:34.300 --> 02:34.990 I command. 02:37.360 --> 02:41.020 I will now paste the command a copy to set up the software repositories. 02:41.890 --> 02:46.810 We will then proceed to execute the same on all the three machines. 03:09.180 --> 03:10.100 OK, so that's done. 03:10.370 --> 03:14.000 The next step is to install Docker's official ZPG keys. 03:14.480 --> 03:15.440 So we will do that. 03:15.560 --> 03:17.180 Also on all the machines. 03:32.320 --> 03:36.700 The next step is to add the Docker APTN repository. 03:37.960 --> 03:40.420 We will then do the same on all the systems. 03:55.280 --> 03:57.560 The next step is to install the DOCA runtime. 03:57.890 --> 04:01.430 We run the commands to install the latest table version of Docker. 04:01.520 --> 04:02.540 As of this recording. 04:04.220 --> 04:09.320 If the version of Docker that is shown here has changed as you're watching this, then feel free to 04:09.320 --> 04:13.520 follow the latest version of documentation to install the latest version of Dr.. 04:15.380 --> 04:16.790 Run that on all the notes. 04:17.540 --> 04:20.540 This may take a few minutes, so wait for that to finish. 04:30.200 --> 04:32.580 The next step is to set up the Dr. Damon. 04:33.140 --> 04:38.720 For this, we create a Damon Dodd Jason file and then create a directory for the doctor service. 05:08.670 --> 05:15.720 We then run the system a demon reload and restart Docker command to load and start the Docker service. 05:24.180 --> 05:30.690 To verify Docker's installed, run the system, cuttle status, dockyard service command and verify 05:30.690 --> 05:31.500 that it is running. 05:32.160 --> 05:35.600 Confirmed that that's the case on all the three notes. 05:37.260 --> 05:42.660 We now go back to the documentation page to proceed with the installation of cabernets components using 05:42.910 --> 05:43.350 rubidium. 05:45.380 --> 05:51.920 The next step is to install the cabinet is related packages such as the two BDM Cube led and cube cuddle 05:52.040 --> 05:52.880 on all the notes. 05:53.600 --> 05:57.590 The cube, the end tool is used to bootstrap the cluster cube. 05:57.590 --> 06:02.270 That is the process that's responsible to manage pods and containers on the note. 06:02.360 --> 06:08.420 And the Cube Cuttle utility is the components command line tool for this run the commands to update 06:08.420 --> 06:11.030 repository and install the required packages. 06:19.580 --> 06:22.350 Run these on all the notes and wait for it to finish. 06:42.020 --> 06:48.170 The next section about configuring Seagram driver is not applicable when using Docker as QB, GM will 06:48.260 --> 06:51.720 automatically detect the group driver for the Kubla. 06:53.120 --> 06:59.150 If you're not using Docker, then we must follow the step to specify the secret driver so we can skip 06:59.150 --> 06:59.840 this for now. 07:00.950 --> 07:04.940 The next step is to configure the QB GM cluster by clicking on this link. 07:06.530 --> 07:10.370 This takes us to the cluster creation process using cubie a.T.M. 07:12.770 --> 07:15.740 The first phase is to initialize control plane node. 07:17.150 --> 07:21.890 The first step in that is only applicable if we are deploying a highly available cluster. 07:22.310 --> 07:23.570 In this demo, we are not. 07:23.840 --> 07:25.460 We just have a single master node. 07:25.850 --> 07:27.110 So we will skip that for now. 07:28.010 --> 07:31.300 The next step is to choose a part network, add on. 07:31.820 --> 07:32.630 And when we do that. 07:32.810 --> 07:35.390 Decide what is network IP address range. 07:35.420 --> 07:36.870 We are going to use for the port. 07:37.730 --> 07:42.260 There are multiple network options available for networking between ports in a coronets cluster. 07:42.320 --> 07:47.990 So if you click on this link, which takes you down in that page today, pertinent Roxette section, 07:48.530 --> 07:54.430 you will see different options for configuring a network such as Kalikow, Psyllium Quantitive, Kue, 07:54.450 --> 07:55.970 Browder, Veev, etc.. 07:56.540 --> 08:01.550 In this case, we will make use of Weev and we can choose a network range that does not conflict with 08:01.550 --> 08:02.760 the network of the nodes. 08:03.110 --> 08:08.450 Remember that we configure the nodes to be in the 190 to that 168 or 56 network. 08:08.900 --> 08:14.180 We will use a network sider that's different from that range for parts. 08:14.270 --> 08:19.040 We will use tender to 44 dot zero zero slash 16 network. 08:20.610 --> 08:24.750 The third step can be ignored as well, since we are using Docker as our container runtime. 08:24.840 --> 08:31.410 But in case you're using a different one, you may use this option to specify that the fourth step is 08:31.410 --> 08:32.640 what we will configure. 08:32.940 --> 08:39.360 We must specify the cabinet is API servers, IP address as the API server advertize address. 08:40.170 --> 08:45.930 This is so that the API server listens on that on the correct static IP address. 08:46.050 --> 08:51.990 We have set on the master node which will make the API server accessible to the worker nodes on any 08:51.990 --> 08:53.850 other clients on that IP address. 08:55.210 --> 08:59.950 Once we have decided the values for the options, we can proceed with initializing the cluster, using 08:59.950 --> 09:01.680 the Cube Edman in its command. 09:02.560 --> 09:04.330 We will run this on the master node. 09:04.450 --> 09:10.120 Remember, this step must only be run on the master node because that's where all the cluster components 09:10.120 --> 09:11.960 have to be installed and initialized. 09:12.820 --> 09:16.240 We copy and paste the cube admin in his command on the master node. 09:16.660 --> 09:21.840 We will then pass in all the required parameters such as the pod network spider, which will be tender 09:21.850 --> 09:24.220 to 44 dodgier Arturo's last 16. 09:28.260 --> 09:33.850 And the API server advertize address is going to be the static IP address of the master node. 09:37.830 --> 09:43.260 Which will be one only to 168 dot fifty six dot two, which is the IP address of the master. 09:43.890 --> 09:48.150 Now if you're not sure about the IP address of the matter node, we can double check that. 09:48.450 --> 09:56.310 So I will for now comment this command so that it is not executed and that I can later access it African 09:56.310 --> 09:57.270 from the IP address. 09:58.050 --> 10:02.040 I will then run the I have conflict command to confirm the IP address of the node. 10:02.940 --> 10:05.520 I can confirm that it is the correct IP address. 10:07.780 --> 10:10.120 I will now run the cube idiom in its command. 10:10.690 --> 10:15.100 It runs a set of pre-flight checks to make sure all prerequisites are in place. 10:15.580 --> 10:17.020 So let's give it some time to run. 10:19.340 --> 10:21.350 The checks are complete and everything looks good. 10:22.040 --> 10:27.280 So we proceed with the creation of security certificates and installation of the various components. 10:29.550 --> 10:32.070 We give it some more time for the insulation to finish. 10:33.060 --> 10:34.650 Now the insulation is complete. 10:35.580 --> 10:41.670 We will now perform the post installation tasks as the output states to start the cluster. 10:41.700 --> 10:44.130 You need to run the following as a regular user. 10:44.610 --> 10:46.850 So we have been running things as the route user. 10:46.890 --> 10:52.440 So we will run the logout command to log out and become the regular user. 10:53.100 --> 10:58.410 Once we are a regular user, we must create a directory under the user's home directly and copy the 10:58.530 --> 10:59.670 admin dot com file. 11:00.710 --> 11:05.860 The admin, not con file, has the necessary information and credentials required to access the cabinet 11:05.970 --> 11:08.790 cluster using the Cube Cuttle command line utility. 11:09.240 --> 11:13.440 It must be placed in the user's home directory under the DOT Cube directory. 11:14.040 --> 11:20.370 So we are on this command to create the DOT Cube directory and copy the admin dot com file into it and 11:20.370 --> 11:22.470 also set the right ownership on it. 11:24.170 --> 11:27.800 The next step is to deploy a part network to the cluster. 11:28.490 --> 11:32.510 Earlier, we decided that we will use Weev as our port network solution. 11:33.860 --> 11:34.880 So we need to do that. 11:36.120 --> 11:41.370 After the port network solution is set up, we will have the worker node's join the cluster using the 11:41.370 --> 11:42.390 command given here. 11:43.170 --> 11:46.400 Keep a out of the command that will be used to join the work. 11:46.420 --> 11:47.520 Noticed the cluster. 11:48.610 --> 11:54.250 I'm just going to copy and echo the command to my screen terminal so that it is available in the terminal 11:54.250 --> 11:56.350 history and I can retrieve it later. 11:56.770 --> 11:59.650 Or you may just copy it to an external text editor. 12:01.070 --> 12:04.620 Let's run the Cucuta's get node's command to check the status of the cluster. 12:04.640 --> 12:09.590 Now we see that the cluster consists of the cube master node only. 12:09.740 --> 12:11.420 And the status is not ready. 12:11.450 --> 12:15.680 As of now, the version is one point eighteen point three. 12:16.100 --> 12:21.490 The reason is not ready is because we do not have a port network solution for this. 12:21.500 --> 12:28.490 We go back to the documentation side and go to the port network section, select Weev and copy the command 12:28.520 --> 12:29.040 to install. 12:29.070 --> 12:29.420 We've. 12:32.760 --> 12:34.740 Pasted on the master note and executed. 12:39.180 --> 12:44.100 We see that the port network solution is being installed and all the required components are created. 12:44.940 --> 12:46.300 It creates a service account. 12:46.360 --> 12:48.810 Rolls, roll bindings, deman sets, etc.. 12:49.830 --> 12:53.940 We discuss a lot about each of these in these certified as administrator course. 12:54.270 --> 13:00.270 We have a section just for networking where we go from the absolute basics of network all the way to 13:00.300 --> 13:01.980 how a weave solution works. 13:02.550 --> 13:03.360 So check that out. 13:03.750 --> 13:07.980 If you have time for now, let's proceed with adding the worker nodes to the cluster. 13:08.640 --> 13:10.830 For this, we use the command we saved earlier. 13:11.430 --> 13:14.070 We will copy it and run it on both the worker notes. 13:28.460 --> 13:31.580 We see that the node has successfully joined the cluster. 13:32.740 --> 13:34.520 Now we are on the KUKA to get notes. 13:34.540 --> 13:37.300 Command on the master note and we will check the status. 13:37.870 --> 13:41.040 It may take a few minutes for the worker notes to be in a ready state. 13:41.080 --> 13:42.430 So let's monitor that. 13:46.650 --> 13:48.780 We now see that they are in a red state. 13:49.210 --> 13:51.480 Our cabinet is cluster is now ready. 13:52.260 --> 13:54.600 We can now test by creating some objects. 13:55.200 --> 14:00.870 Let's create a pot using the cube cuttle run engine next command and specify the engine X image. 14:07.750 --> 14:11.740 We see it's created a pod by running the tube to get pods command. 14:13.240 --> 14:14.900 The parts are still being created. 14:15.140 --> 14:19.670 So we wait for a few minutes and we will see that it's now in a running state. 14:20.630 --> 14:24.020 We will not delete it using the Cucuta delete part command. 14:26.730 --> 14:28.200 Well, that's it for this demo. 14:28.530 --> 14:29.430 Thank you for watching.