WEBVTT 00:00.570 --> 00:01.740 Instructor: In the last section, we used Helm 00:01.740 --> 00:05.100 to install Ingress-NGINX inside of our project. 00:05.100 --> 00:06.210 Now that we've got that installed, 00:06.210 --> 00:08.670 I want you to refresh the page. 00:08.670 --> 00:10.110 So I'm gonna refresh this entire thing. 00:10.110 --> 00:12.060 I'm gonna say yes, go ahead and reload, 00:13.890 --> 00:17.100 and then I'm gonna flip over to the Workloads tab over here. 00:17.100 --> 00:19.020 Remember, the workloads tab is where we're going 00:19.020 --> 00:21.390 to eventually see a list of all of our deployments. 00:21.390 --> 00:22.620 So we can now very easily see 00:22.620 --> 00:25.410 that we have something here called the Ingress controller, 00:25.410 --> 00:27.570 and our Ingress default backend. 00:27.570 --> 00:30.200 Remember, the Ingress controller is the pod, 00:30.200 --> 00:32.730 or in this case, the deployment that manages the pod, 00:32.730 --> 00:34.380 that runs the actual controller 00:34.380 --> 00:36.780 that's going to read our Ingress config file 00:36.780 --> 00:39.420 and then set up NGINX appropriately. 00:39.420 --> 00:42.480 The default backend is, as it says, a default backend 00:42.480 --> 00:44.943 that has a series of health checks inside of it. 00:45.960 --> 00:48.120 If we were doing things really, really well, 00:48.120 --> 00:50.460 we would set up a certain number of routes 00:50.460 --> 00:51.990 inside of our Express API 00:51.990 --> 00:55.320 to associate the health of our cluster with our actual API 00:55.320 --> 00:57.180 as opposed to this default backend, 00:57.180 --> 01:00.393 but in this case, using the default backend, totally fine. 01:01.350 --> 01:02.850 Now, the other thing I wanna show you really quickly 01:02.850 --> 01:05.280 is the Services tab over here. 01:05.280 --> 01:07.830 Now, if you see something here that says Load Balancer 01:07.830 --> 01:09.090 and you see these two sets 01:09.090 --> 01:10.800 of numbers next to it, that's great. 01:10.800 --> 01:13.140 If you do not see two sets of numbers right here, 01:13.140 --> 01:16.080 then pause the video right now for, like, a couple minutes 01:16.080 --> 01:19.110 and try refreshing the page again in a couple minutes. 01:19.110 --> 01:21.570 After a little bit, you'll eventually see two sets 01:21.570 --> 01:23.310 of numbers appear right here. 01:23.310 --> 01:24.660 These two sets of numbers that you see 01:24.660 --> 01:26.550 are the actual IP addresses 01:26.550 --> 01:29.460 that we're going to eventually use to access our project. 01:29.460 --> 01:30.780 And so right now, as a matter of fact, 01:30.780 --> 01:33.120 you can click on the colon 80 address, 01:33.120 --> 01:35.040 or the colon 80 port right there, 01:35.040 --> 01:37.680 and it'll open up a new tab at that IP address, 01:37.680 --> 01:40.863 and you'll see default backend 404 appear on the screen. 01:41.970 --> 01:44.370 This message right here is being created by, 01:44.370 --> 01:46.410 as you might guess, the default backend 01:46.410 --> 01:48.000 that was created for us. 01:48.000 --> 01:49.440 That's the purpose of the default backend. 01:49.440 --> 01:51.210 Not only does it provide a health check, 01:51.210 --> 01:53.790 it also provides a default 404 page 01:53.790 --> 01:54.960 that our users will go to 01:54.960 --> 01:58.590 if some route cannot be found inside of our application. 01:58.590 --> 02:00.150 AlL right, so eventually we're going 02:00.150 --> 02:02.070 to use this IP address right here 02:02.070 --> 02:04.680 to get access to our application later on. 02:04.680 --> 02:05.670 Now, before we continue, 02:05.670 --> 02:07.560 there's one other quick thing I wanna show you. 02:07.560 --> 02:10.260 If you go to the Navigation menu up here, 02:10.260 --> 02:12.060 we'll then scroll down a little bit, 02:13.440 --> 02:16.050 and inside of here, I always forget exactly where it is, 02:16.050 --> 02:16.883 ah, here we go. 02:16.883 --> 02:19.470 Network Services under the Networking section. 02:19.470 --> 02:21.330 So, we're gonna go to Network Services 02:21.330 --> 02:24.300 and they'll dump us out on the Load Balancing tab. 02:24.300 --> 02:27.180 This right here is the Google Cloud load balancer 02:27.180 --> 02:29.103 that was created for our cluster. 02:30.150 --> 02:32.100 You can take a look at the load balancer details. 02:32.100 --> 02:33.780 Essentially what it's saying right here 02:33.780 --> 02:35.610 is that the load balancer can be accessed 02:35.610 --> 02:36.990 at this IP address. 02:36.990 --> 02:39.300 This is the same IP we just went to a second ago, 02:39.300 --> 02:41.280 and the load balancer is governing access 02:41.280 --> 02:44.040 to this set of different instances. 02:44.040 --> 02:45.810 The set of instances right here that you see 02:45.810 --> 02:47.250 are different virtual machines. 02:47.250 --> 02:49.170 They represent the three nodes 02:49.170 --> 02:51.360 that belong to our Kubernetes cluster. 02:51.360 --> 02:54.060 So recall, we looked at this diagram a long time ago 02:54.060 --> 02:56.760 when we were talking about Ingress-NGINX and Google Cloud. 02:56.760 --> 02:59.040 We had said that when we use Ingress-NGINX, 02:59.040 --> 03:02.190 it's going to create a Google Cloud load balancer. 03:02.190 --> 03:03.780 So, that's what you're looking at right here. 03:03.780 --> 03:05.820 This is the Google Cloud load balancer 03:05.820 --> 03:08.523 that is not at all native to Kubernetes. 03:09.690 --> 03:14.040 That load balancer is going to get traffic into our node, 03:14.040 --> 03:16.020 or the entire cluster in this case, 03:16.020 --> 03:19.200 and it's gonna point traffic to the Load Balancer Service, 03:19.200 --> 03:20.940 which is a kubernetes service. 03:20.940 --> 03:22.800 It's a type of service, 03:22.800 --> 03:25.080 and that service is directing traffic 03:25.080 --> 03:27.510 to our NGINX Ingress controller, 03:27.510 --> 03:29.010 which is eventually gonna send traffic off 03:29.010 --> 03:30.960 to all of our different deployments. 03:30.960 --> 03:31.890 All right, so it's kind fun 03:31.890 --> 03:34.050 to see this stuff all finally come together. 03:34.050 --> 03:35.400 Now, the very last thing we have to do 03:35.400 --> 03:37.680 is actually deploy our application. 03:37.680 --> 03:40.500 So, we get all the rest of our infrastructure on here. 03:40.500 --> 03:41.460 So, let's take a quick break. 03:41.460 --> 03:42.600 When we come back to the next section, 03:42.600 --> 03:44.760 we're gonna finally deploy our app. 03:44.760 --> 03:47.310 So, quick pause, and I'll see you in just a moment.