1
00:00:04,800 --> 00:00:12,270
And by the way, using this API server service, you could actually manage an entire Kubernetes cluster.

2
00:00:12,870 --> 00:00:14,160
How is it done?

3
00:00:14,250 --> 00:00:19,320
It is done by using cube steel or cube control.

4
00:00:20,390 --> 00:00:29,120
And Kub Control is a separate command line tool which allows you to connect to specific Kubernetes cluster

5
00:00:29,120 --> 00:00:31,040
and manage it remotely.

6
00:00:32,259 --> 00:00:36,910
And Cuba at Yale could be running even on your local computer.

7
00:00:36,910 --> 00:00:42,040
And using such a little tool, you could manage a remote Kubernetes cluster.

8
00:00:42,280 --> 00:00:50,350
And using such tool, you actually connect using rest API to API server service on the master node.

9
00:00:50,350 --> 00:00:54,370
And such communication happens over https.

10
00:00:54,880 --> 00:01:01,750
By the way, other nodes in the cluster, I mean worker nodes communicate with master node in the same

11
00:01:01,750 --> 00:01:02,470
fashion.

12
00:01:03,070 --> 00:01:09,580
It means that using such little tool you could manage any remote Kubernetes cluster.

13
00:01:09,580 --> 00:01:12,480
That's it for Kubernetes Architecture Overview.

14
00:01:12,490 --> 00:01:19,120
And now you know that Kubernetes cluster consists of the nodes and the one of the nodes is Master Node,

15
00:01:19,120 --> 00:01:23,530
and it manages other nodes which are called worker nodes.

16
00:01:24,040 --> 00:01:30,700
On each node there are ports and the ports are created automatically by Kubernetes.

17
00:01:30,700 --> 00:01:36,460
And inside of the port there are containers, usually just a single container per port.

18
00:01:37,120 --> 00:01:44,980
Also, please keep in mind that all containers inside of the port share namespaces of that port like

19
00:01:44,980 --> 00:01:47,470
volumes or network IP address.

20
00:01:48,340 --> 00:01:54,970
Also, ports are smallest units in Kubernetes, and the ports could be created that could be removed,

21
00:01:54,970 --> 00:01:58,150
could be moved from one node to another.

22
00:01:58,150 --> 00:02:04,990
This happens automatically without your intervention, but you have to design your application with

23
00:02:04,990 --> 00:02:06,040
this in mind.

24
00:02:06,040 --> 00:02:09,160
Both could be deleted on any moment of time.

25
00:02:10,669 --> 00:02:15,330
Also there are different services which are running on different nodes, for example.

26
00:02:15,350 --> 00:02:23,570
API server service is a central point of communication between master node and other worker nodes and

27
00:02:23,570 --> 00:02:30,500
also using such API server service, you actually could manage actual Kubernetes cluster using Kupe

28
00:02:30,500 --> 00:02:36,410
CTO tool, which has to be installed, for example, on your computer if you perform management from

29
00:02:36,410 --> 00:02:37,250
your computer.

30
00:02:38,500 --> 00:02:39,140
All right.

31
00:02:39,490 --> 00:02:46,570
I don't want to dive deeper into the details of the Kubernetes, because this is very complicated tool,

32
00:02:46,570 --> 00:02:50,740
and I want to focus more on practical tasks instead.

33
00:02:50,770 --> 00:02:57,430
That's why now, after such overview, we will dive together with you into the practice and perform

34
00:02:57,430 --> 00:02:59,800
different practical tasks together.

35
00:02:59,830 --> 00:03:06,460
For example, we will create deployments, services, scale deployments, create custom Docker image

36
00:03:06,460 --> 00:03:09,730
and create deployment based on that image and so on.