1
00:00:04,830 --> 00:00:13,620
Now let's keep this window open here and let's increase quantity of the bolts in our deployment.

2
00:00:13,650 --> 00:00:15,900
Let's scale our deployment.

3
00:00:16,350 --> 00:00:19,850
I'll open up new tab in the term application.

4
00:00:19,860 --> 00:00:22,750
You could open a new terminal window if you're on windows.

5
00:00:22,770 --> 00:00:28,340
I'll use key combination command in order to open new tab here and here in the new tab.

6
00:00:28,350 --> 00:00:34,380
If I enter key, I will say error command not found because alias works only in this tab.

7
00:00:34,410 --> 00:00:36,960
That's why let's create alias once again.

8
00:00:37,050 --> 00:00:40,570
Alias K equals sign kub still.

9
00:00:40,590 --> 00:00:46,810
By the way, you could omit double quotes here if command consists only of single word.

10
00:00:46,830 --> 00:00:50,910
So let me remove those double quotes like that alias was created.

11
00:00:50,910 --> 00:00:52,860
And now let's k get.

12
00:00:54,120 --> 00:00:55,200
And here I see.

13
00:00:55,200 --> 00:01:00,930
Same name of the port, which I saw here in the answer from the web server.

14
00:01:01,320 --> 00:01:03,990
Let's now scale this deployment.

15
00:01:04,019 --> 00:01:04,500
Recap.

16
00:01:04,500 --> 00:01:06,680
That name of our deployment is.

17
00:01:07,840 --> 00:01:09,420
Gay et se web.

18
00:01:09,430 --> 00:01:10,030
Hello.

19
00:01:10,060 --> 00:01:15,040
Here was the name of the deployment and now it currently has just single board.

20
00:01:15,490 --> 00:01:16,810
Let's scale it.

21
00:01:16,960 --> 00:01:19,510
Gay scale deployment.

22
00:01:20,480 --> 00:01:21,400
Gates.

23
00:01:21,410 --> 00:01:23,000
Webb Hello.

24
00:01:23,090 --> 00:01:27,590
And I would like to scale deployment to, let's say, four replicas.

25
00:01:27,620 --> 00:01:28,640
Let's go ahead.

26
00:01:28,670 --> 00:01:30,620
Deployment was scaled.

27
00:01:30,650 --> 00:01:32,600
Let's now get ports.

28
00:01:32,640 --> 00:01:34,070
K get ports.

29
00:01:34,730 --> 00:01:36,470
Now, there were four ports.

30
00:01:36,470 --> 00:01:38,780
One is still being created.

31
00:01:39,560 --> 00:01:40,780
Let's check back again.

32
00:01:40,790 --> 00:01:43,280
And now all four ports are running.

33
00:01:43,580 --> 00:01:45,610
All of them belong to the same deployment.

34
00:01:45,630 --> 00:01:46,880
Cate as Webb.

35
00:01:46,880 --> 00:01:47,480
Hello.

36
00:01:47,480 --> 00:01:51,530
And each boat, of course, has its own unique IP address.

37
00:01:51,560 --> 00:01:53,690
Let's get details about boats.

38
00:01:54,020 --> 00:01:55,970
Get boats this all white.

39
00:01:56,750 --> 00:02:00,500
And here I see different IP addresses of each boat.

40
00:02:00,920 --> 00:02:07,790
And of course, they differ from the cluster IP, which was created for specific service.

41
00:02:08,090 --> 00:02:11,420
Let's list services, get SVC.

42
00:02:11,540 --> 00:02:22,310
And here as before we see cluster IP for k eight as web hello service and each of those ports is now

43
00:02:22,310 --> 00:02:32,150
available via this cluster IP and Kubernetes will decide which port to choose for each particular request.

44
00:02:32,870 --> 00:02:40,010
Let's now go back to this step where we are inside of the Kubernetes node and try to make connections

45
00:02:40,010 --> 00:02:43,010
to this cluster IP and this port again.

46
00:02:44,330 --> 00:02:47,180
Let's call your terminal here and see your URL.

47
00:02:47,750 --> 00:02:51,330
Now I see response from this port with such name.

48
00:02:51,350 --> 00:02:54,710
If I repeat command, I see response from other port.

49
00:02:55,250 --> 00:02:57,080
Let's repeat command once again.

50
00:02:57,620 --> 00:02:58,610
Once again.

51
00:02:58,880 --> 00:02:59,840
And so on.

52
00:02:59,990 --> 00:03:01,460
I see that now.

53
00:03:01,460 --> 00:03:08,480
A lot is balanced across different ports because here I see responses from different ports.

54
00:03:09,020 --> 00:03:12,770
Different names appear here in the responses.

55
00:03:13,340 --> 00:03:16,460
Different ports serve different requests.

56
00:03:16,820 --> 00:03:19,250
And here are different names of the ports.

57
00:03:20,720 --> 00:03:24,650
That's how distribution of the Lord works in action.

58
00:03:24,650 --> 00:03:30,200
And now using such customarily built Docker image, we were able to prove that.

