1
00:00:04,110 --> 00:00:04,920
All right.

2
00:00:04,920 --> 00:00:06,870
So let's get started with this course.

3
00:00:06,870 --> 00:00:09,630
And I would like to start with a definition.

4
00:00:09,990 --> 00:00:13,740
Kubernetes is container orchestration system.

5
00:00:14,970 --> 00:00:19,860
Using Docker, you could, of course, create container on any computer.

6
00:00:20,070 --> 00:00:26,970
But of course, if you want to create multiple containers on different computers, on different servers,

7
00:00:26,970 --> 00:00:28,890
you could get into the troubles.

8
00:00:29,520 --> 00:00:36,180
Kubernetes allows you to create the containers on different servers, either physical or virtual, and

9
00:00:36,180 --> 00:00:38,010
all of that is done automatically.

10
00:00:38,010 --> 00:00:39,720
Without your intervention.

11
00:00:39,720 --> 00:00:46,500
You just tell Kubernetes how many containers you would like to create based on specific image.

12
00:00:46,950 --> 00:00:53,850
Kubernetes is relatively long world, and it consists of ten different letters, but IT professionals

13
00:00:53,850 --> 00:00:59,220
and software developers are relatively lazy people and they don't like to type much.

14
00:00:59,220 --> 00:01:04,140
That's why such a long word is usually shortened just to three characters.

15
00:01:04,140 --> 00:01:05,519
But how is it done?

16
00:01:06,000 --> 00:01:09,690
Let's have a look at this word between K and S.

17
00:01:09,690 --> 00:01:12,660
There are actually eight different letters.

18
00:01:12,660 --> 00:01:19,980
So number eight, that's why long word Kubernetes could be shortened just to three characters.

19
00:01:20,010 --> 00:01:27,870
k8s so eight represents simply quantity of the letters between starting and end in a letter.

20
00:01:27,870 --> 00:01:32,760
Simple as that, knowing this very simple trick, we could go on.

21
00:01:32,760 --> 00:01:37,710
And now let me explain to you what Kubernetes takes care of.

22
00:01:38,130 --> 00:01:44,760
So Kubernetes takes care of automatic deployment of the containerised applications across different

23
00:01:44,760 --> 00:01:45,630
servers.

24
00:01:45,810 --> 00:01:51,870
And those servers could be either bare metal or physical servers or virtual servers.

25
00:01:51,900 --> 00:01:58,440
Virtual servers option is, of course, more common nowadays, and almost no one uses now bare metal

26
00:01:58,440 --> 00:01:59,190
servers.

27
00:01:59,790 --> 00:02:06,600
So Kubernetes allows you to perform automated deployments across different servers that could be located

28
00:02:06,600 --> 00:02:08,729
even in different parts of the world.

29
00:02:09,810 --> 00:02:16,800
Other than that, Kubernetes also takes care of distribution of the load across those multiple servers,

30
00:02:17,460 --> 00:02:25,890
and this allows you to use your resources efficiently and avoid underutilization or overutilization

31
00:02:25,890 --> 00:02:26,910
of the resources.

32
00:02:27,900 --> 00:02:35,070
Also, Kubernetes takes care of the outer scaling of the deployed applications in case you need to increase,

33
00:02:35,100 --> 00:02:42,000
for example, quantity of the containers which have to be created on different servers and all of that

34
00:02:42,000 --> 00:02:43,560
done automatically.

35
00:02:43,560 --> 00:02:47,400
You just tell when you want to scale up or down.

36
00:02:48,710 --> 00:02:54,410
Also, Kubernetes takes care of the monitoring and health check of the containers.

37
00:02:54,860 --> 00:03:02,810
And in case some containers fail, for some reasons, Kubernetes could automatically replace failed

38
00:03:02,810 --> 00:03:03,740
containers.

39
00:03:03,980 --> 00:03:07,040
And all of that done without your intervention.

40
00:03:07,730 --> 00:03:14,990
As I just told you, Kubernetes deploys containerised applications, and therefore it has to use specific

41
00:03:14,990 --> 00:03:16,730
container runtime.

42
00:03:17,060 --> 00:03:20,840
And Docker is just one of the possible options.

43
00:03:21,500 --> 00:03:31,430
Kubernetes nowadays supports such container runtimes, docker, cry O and container db and such container

44
00:03:31,430 --> 00:03:39,110
runtime, for example, as Docker or O must be running on each of the servers which are included in

45
00:03:39,110 --> 00:03:40,460
the Kubernetes cluster.

46
00:03:41,240 --> 00:03:47,810
And main outcome here is that Kubernetes could be utilised even without Docker at all.

47
00:03:47,840 --> 00:03:54,770
It supports other container runtimes like cry O and container D, and at the end of this course I'll

48
00:03:54,770 --> 00:04:01,190
demonstrate to you how to change container runtime and move from Docker, for example, to cry o.

49
00:04:02,590 --> 00:04:10,510
So now let's get started with terminology and architecture of Kubernetes, and let's start with port.

