WEBVTT 00:00.560 --> 00:06.500 Let us now look at another type of service known as the load balancer type. 00:07.730 --> 00:14.930 So we have seen the node port service that helps us make an external facing application available on 00:14.930 --> 00:16.640 a port on the worker notice. 00:17.300 --> 00:23.040 So let's turn our focus to the front end applications, which are the voting app and the result app. 00:23.930 --> 00:28.820 Now, we know that these pods are hosted on the worker nodes in a cluster. 00:29.150 --> 00:32.240 So let's say we have a four node cluster. 00:32.810 --> 00:40.400 And to make the applications accessible to external users, we create these services of type node port. 00:41.150 --> 00:48.410 Now the services with type node port help in receiving traffic on the ports, on the notes and routing 00:48.410 --> 00:50.090 the traffic to the respective parts. 00:50.960 --> 00:56.600 But what you are l would you give your end users to access the applications and you could access any 00:56.600 --> 01:02.630 of these two applications using IP of any of the nodes and the high port. 01:04.140 --> 01:10.640 The services exposed on, so that would be for IP and port combinations for the voting app and for IP 01:10.640 --> 01:12.530 and port combination for the result app. 01:13.470 --> 01:18.330 So not bad, even if your ports are only hosted on two of the nodes. 01:18.810 --> 01:24.480 There will still be accessible on the eyepiece of all the notes in the cluster say the parts for the 01:24.480 --> 01:28.130 voting app are only deployed on the nodes with IP 70 and 71. 01:28.650 --> 01:31.890 There would still be accessible on the ports of all the nodes in the cluster. 01:32.610 --> 01:35.100 So that's how our service is configured. 01:35.610 --> 01:36.990 So you would share these. 01:36.990 --> 01:40.150 You are El's to your users to access the application. 01:40.590 --> 01:42.330 But that's not what the end users want. 01:42.420 --> 01:50.340 They need a single you URL like example, voting app, dot com or the example a result app dot com to 01:50.340 --> 01:51.420 access the application. 01:51.840 --> 01:53.340 So how do you achieve that? 01:53.820 --> 02:01.290 Now one way to achieve this is to create a new VM for a load balancer purpose and install and configure 02:01.290 --> 02:10.730 a suitable load balancer on it like a proxy or engine X, etc. then configure the load balancer to route 02:10.740 --> 02:12.520 traffic to the underlying notes. 02:13.590 --> 02:20.400 Now, setting all of that external load balancing and then maintaining and managing, that can be a 02:20.400 --> 02:21.340 tedious task. 02:22.570 --> 02:30.670 However, if we were on a supported cloud platform like Google Cloud or NWS or Azure, I could leverage 02:30.700 --> 02:33.850 the native load balancer off that cloud platform. 02:34.660 --> 02:41.410 Cooper Netas has support for integrating with the native load balancers of certain cloud providers and 02:41.410 --> 02:43.900 configuring and configuring that for us. 02:44.530 --> 02:51.970 So all you need to do is set the service type for the friend and services to load balancer instead of 02:51.970 --> 02:52.540 node port. 02:53.200 --> 02:57.250 Now remember that this only works with support cloud platforms. 02:57.760 --> 03:01.790 So GCP, it appears and and as your are definitely supported. 03:02.200 --> 03:04.780 So if you set the type of service to load balancer. 03:06.400 --> 03:13.450 In an unsupportive environment like a virtual box or, you know, any other environment, then it would 03:13.450 --> 03:20.740 have the same effect as setting a two note port where, you know, the services are exposed on a high 03:20.740 --> 03:23.260 end port on the notes there. 03:23.350 --> 03:28.060 It just won't do any kind of external load balancer configuration. 03:28.500 --> 03:28.690 Right. 03:28.830 --> 03:35.740 So later on, when we walked through the demos of deploying our application on cloud platforms, we 03:35.740 --> 03:37.540 will see this in action. 03:37.910 --> 03:38.150 Right. 03:38.530 --> 03:39.340 So that's it for now. 03:39.650 --> 03:41.620 I will see you in the next lecture.