1 00:00:04,680 --> 00:00:10,470 And the one more option which I would like to show you in terms of creation of the service is a load 2 00:00:10,470 --> 00:00:11,370 balancer. 3 00:00:11,400 --> 00:00:14,160 Let's create a load balancer service. 4 00:00:14,160 --> 00:00:21,510 And for that first, let's delete existing service k delete SVC service k eight as. 5 00:00:21,900 --> 00:00:22,530 Hello. 6 00:00:24,380 --> 00:00:25,730 Service was removed. 7 00:00:26,050 --> 00:00:27,440 Get SBC. 8 00:00:27,650 --> 00:00:29,270 There was no more such service. 9 00:00:29,270 --> 00:00:31,760 And let's create a service of type. 10 00:00:31,790 --> 00:00:32,840 Load balancer. 11 00:00:33,620 --> 00:00:34,030 Okay. 12 00:00:34,140 --> 00:00:38,280 Expose deployment gate as web. 13 00:00:38,330 --> 00:00:39,170 Hello. 14 00:00:39,440 --> 00:00:41,180 Here, let's add type. 15 00:00:41,990 --> 00:00:43,610 Load balancer. 16 00:00:44,400 --> 00:00:46,050 What's called case notation again. 17 00:00:46,050 --> 00:00:51,000 And let's add fourth option and its value will be 3000. 18 00:00:51,030 --> 00:00:52,110 Same as before. 19 00:00:52,320 --> 00:00:54,110 Let's create such service. 20 00:00:54,120 --> 00:01:03,090 Service was created k get as we see now I see that there is service of type load balancer here with 21 00:01:03,090 --> 00:01:11,070 cluster IP, but external IP here is pending and you will see here pending if you are using mini cube. 22 00:01:11,160 --> 00:01:18,810 But when you deploy your applications somewhere in the cloud using one of the cloud providers like Amazon, 23 00:01:18,810 --> 00:01:24,660 Google Cloud, etc. here you will see load balancer IP address assigned automatically. 24 00:01:25,320 --> 00:01:34,890 But in our case, using mini cube is behavior is similar to node port and here we will still be able 25 00:01:34,890 --> 00:01:41,070 to connect to our deployment using IP address of the node and if I enter now mini cube. 26 00:01:42,150 --> 00:01:43,080 Service. 27 00:01:43,440 --> 00:01:45,000 Gay AIDS web. 28 00:01:45,030 --> 00:01:45,780 Hello. 29 00:01:46,780 --> 00:01:52,510 I lost a connection which is made to IP address of the node and here was again random port which was 30 00:01:52,510 --> 00:01:54,100 generated here. 31 00:01:54,400 --> 00:01:56,170 Here was this random port. 32 00:01:56,320 --> 00:02:01,170 All right, let's continue and let's keep this service and this deployment in place. 33 00:02:01,180 --> 00:02:05,010 Recap that we have single service here, which we created before. 34 00:02:05,020 --> 00:02:06,610 It is k eight as a web. 35 00:02:06,610 --> 00:02:07,030 Hello. 36 00:02:07,030 --> 00:02:15,220 And this type now is load balancer and there is a single deployment k get deployed and this name is 37 00:02:15,220 --> 00:02:16,480 K eight as web. 38 00:02:16,480 --> 00:02:17,020 Hello. 39 00:02:17,020 --> 00:02:21,610 And now this deployment has four different ports available for use. 40 00:02:22,510 --> 00:02:24,730 We could read the details about this deployment. 41 00:02:24,730 --> 00:02:27,520 K describe deployment. 42 00:02:28,460 --> 00:02:29,980 Kate s Webb. 43 00:02:29,990 --> 00:02:30,680 Hello. 44 00:02:31,250 --> 00:02:33,620 And here are details of this deployment. 45 00:02:33,620 --> 00:02:38,480 By the way, at the end here I see logs related to scaling of replica set. 46 00:02:38,480 --> 00:02:44,450 Initially quantity of the replicas was one and later we scaled it to four. 47 00:02:44,480 --> 00:02:49,790 If you want, you could try to scale it to any other number if you want to do so above. 48 00:02:49,790 --> 00:02:52,970 I see that this deployment has a name gate as well. 49 00:02:53,000 --> 00:02:53,560 Hello. 50 00:02:53,570 --> 00:03:00,360 Namespace is default labels annotations selector replicas desired for updated for. 51 00:03:00,410 --> 00:03:01,610 Available for.