WEBVTT

00:01.398 --> 00:03.811
In this lecture,
we will look at the kubeadm tool,

00:03.811 --> 00:06.654
which could be used to bootstrap
a Kubernetes cluster.

00:06.654 --> 00:09.315
The kubeadm tool helps us set up
a multi-node cluster

00:09.315 --> 00:11.750
using Kubernetes best practices.

00:11.750 --> 00:16.451
As we discussed, the Kubernetes cluster
consists of various components

00:16.451 --> 00:21.868
including the cube API server,
etcd, the controllers, et cetera.

00:21.992 --> 00:25.206
We've seen some of the requirements
around security and certifications

00:25.206 --> 00:28.339
to enable communication between
all of the components.

00:28.339 --> 00:30.269
Installing all of these various components

00:30.269 --> 00:32.592
individually across different nodes

00:32.592 --> 00:35.676
and modifying all of the necessary
configuration files

00:35.676 --> 00:37.790
to make sure all the components
point to each other

00:37.790 --> 00:41.254
and setting up certificates
to make it work is a tedious task.

00:41.254 --> 00:46.161
The kubeadm tool helps us by taking care
of all of these tasks.

00:46.161 --> 00:48.639
Let's go through the steps to set up
a Kubernetes cluster

00:48.639 --> 00:51.496
using the kubeadm tool at a high level.

00:51.496 --> 00:55.699
First, you need to have multiple systems
or VMs provisioned.

00:55.699 --> 00:58.382
We're going to need a couple of nodes
for our Kubernetes cluster.

00:58.382 --> 01:01.698
These can be once again physical
or virtual machines.

01:01.698 --> 01:05.095
In the next video, in the demo,
we'll actually go over

01:05.095 --> 01:06.424
how to set this up on your laptop,

01:06.424 --> 01:09.077
and you'll see that it's going be
actually very easy.

01:09.077 --> 01:11.504
Once all of the nodes are provisioned,

01:11.504 --> 01:13.735
you're going to have to designate
one as the master

01:13.735 --> 01:16.217
and the rest as worker nodes.

01:16.217 --> 01:20.519
The next step after that is to install
a container runtime on the hosts.

01:20.519 --> 01:23.235
We will specifically be using container D,

01:23.235 --> 01:27.215
and so we're going to install container D
on all of the nodes.

01:27.215 --> 01:31.063
After that, we'll have to install
the kubeadm tool on all the nodes.

01:31.063 --> 01:34.893
The kubeadm tool helps us
bootstrap the Kubernetes solution

01:34.893 --> 01:37.265
by installing all of the necessary
components

01:37.265 --> 01:40.405
on the right nodes in the right order.

01:40.405 --> 01:43.591
Following that, we have to then initialize
the master server.

01:43.591 --> 01:46.997
During this process,
all of the required components

01:46.997 --> 01:50.297
are installed and configured
on the master server.

01:50.297 --> 01:53.452
Then once the master server
has been initialized,

01:53.452 --> 01:57.312
but prior to joining
the worker nodes to the cluster,

01:57.312 --> 02:00.540
you must ensure
that the network prerequisites are met.

02:00.540 --> 02:03.080
Normal network connectivity
is not enough for this.

02:03.080 --> 02:05.316
Kubernetes requires
a special networking solution

02:05.316 --> 02:10.105
between the master and worker nodes
called the POD Network.

02:10.105 --> 02:11.786
Once the POD Network is set up,

02:11.786 --> 02:17.619
we are all set to go on having
the worker nodes join the master node.

02:18.534 --> 02:19.948
Once they've joined the master node,

02:19.948 --> 02:22.883
we can then move on
to deploying our application

02:22.883 --> 02:25.550
onto the Kubernetes environment.

02:25.822 --> 02:29.505
We will now see a demo of setting up
a Kubernetes cluster

02:29.505 --> 02:33.589
using the kubeadm tool
on our local environment.