1
00:00:04,380 --> 00:00:11,160
Now let's try to scale this deployment and increase quantity of the ports inside of the deployment.

2
00:00:11,190 --> 00:00:17,190
Now there is just a single port for that we could utilize following Command Hub City shortly.

3
00:00:17,460 --> 00:00:21,890
In our case scale, we would like to scale deployment.

4
00:00:22,440 --> 00:00:23,040
Right here.

5
00:00:23,040 --> 00:00:23,910
Deployment.

6
00:00:24,390 --> 00:00:29,010
Name of the deployment in our case is that deployment.

7
00:00:30,230 --> 00:00:35,750
And afterwards, let's specify quantity of the replicas we would like to have in this deployment right

8
00:00:35,750 --> 00:00:36,200
now.

9
00:00:36,380 --> 00:00:38,180
Now there are just a single replica.

10
00:00:38,540 --> 00:00:42,770
In order to specify desired quantity of the replicas, we could add here.

11
00:00:42,770 --> 00:00:49,080
Option replicas and after equal sign, specify quantity of the replicas.

12
00:00:49,100 --> 00:00:52,630
Let's say we want to scale to five replicas.

13
00:00:52,640 --> 00:00:56,570
Let's enter five here and let's scale our deployment.

14
00:00:56,990 --> 00:01:01,700
Deployment was scaled and now let's enter command k get put.

15
00:01:02,210 --> 00:01:08,510
And I see that there are four new containers which are currently being created.

16
00:01:09,920 --> 00:01:17,060
Here was one put second, third and fourth port, and this boat is still running.

17
00:01:17,360 --> 00:01:21,070
In a moment, you should see that all five posts will be running.

18
00:01:21,080 --> 00:01:22,070
Here they are.

19
00:01:23,410 --> 00:01:28,630
We just scaled our deployment to five different replicas.

20
00:01:28,630 --> 00:01:34,900
And now there are five different ports running right now inside of our Kubernetes cluster.

21
00:01:35,290 --> 00:01:37,510
And notice how easy it is.

22
00:01:37,780 --> 00:01:40,720
We did not create those ports manually.

23
00:01:40,780 --> 00:01:44,470
Kubernetes scaled this deployment automatically for us.

24
00:01:46,060 --> 00:01:49,430
Notice that all those sports have the same prefix.

25
00:01:49,450 --> 00:01:57,310
It is name of the replica set all those sports belong to and those parts are different for different

26
00:01:57,310 --> 00:01:57,850
pots.

27
00:01:58,600 --> 00:02:00,760
And again, all pots are running.

28
00:02:00,910 --> 00:02:05,540
Let's also read the about those sports which will include IP addresses.

29
00:02:05,560 --> 00:02:06,350
Let's add here.

30
00:02:06,370 --> 00:02:07,180
Option dash.

31
00:02:07,180 --> 00:02:08,530
Oh white.

32
00:02:09,470 --> 00:02:16,520
And I will see that each board has different IP address here, here, here, here or here.

33
00:02:17,360 --> 00:02:23,900
And all those ports were created just on single node mini queue because again, we have just single

34
00:02:23,900 --> 00:02:25,010
node cluster.

35
00:02:26,270 --> 00:02:32,720
If you were running multiple nodes, of course load would be distributed across different nodes and

36
00:02:32,720 --> 00:02:37,490
you would see that both were assigned to different nodes.

37
00:02:37,520 --> 00:02:38,100
All right.

38
00:02:38,120 --> 00:02:44,390
Now, let's try to scale down quantity of the replicas in this deployment from five to, let's say,

39
00:02:44,390 --> 00:02:44,930
three.

40
00:02:45,020 --> 00:02:49,610
Let's go back to this command K scale deployment, engine X deployment.

41
00:02:49,610 --> 00:02:55,390
And here, let's specify quantity of the replicas as three like that deployment was scaled.

42
00:02:55,400 --> 00:03:01,040
Let's get ports and I see that now there are only three ports up and running.

43
00:03:01,430 --> 00:03:03,980
Two ports were removed.