WEBVTT 00:01.110 --> 00:02.670 -: Now that you've got your domain purchased, 00:02.670 --> 00:04.710 we're going to do a little bit of setup 00:04.710 --> 00:08.040 and make sure that it points to our Kubernetes cluster IP, 00:08.040 --> 00:10.830 specifically the IP address that you can find by going back 00:10.830 --> 00:14.700 to your Kubernetes cluster dashboard, going to Services 00:14.700 --> 00:17.760 and then finding the Ingress Controller right here. 00:17.760 --> 00:20.250 So that's the IP address that we're going to make use of. 00:20.250 --> 00:21.510 And we're gonna make sure that going 00:21.510 --> 00:23.850 to our domain name that we just purchased is going 00:23.850 --> 00:26.280 to point at that IP address. 00:26.280 --> 00:29.400 Now, to set this up I'm gonna find the DNS settings 00:29.400 --> 00:31.890 for the domain that I just purchased. 00:31.890 --> 00:34.080 So I'll click on DNS and then we'll scroll 00:34.080 --> 00:36.300 to the bottom of this page. 00:36.300 --> 00:38.670 So I'm gonna go down to the bottom 00:38.670 --> 00:41.850 and I'll find Custom Resource Records. 00:41.850 --> 00:44.700 We're going to set up two separate records in total. 00:44.700 --> 00:46.650 The first one is going to make sure that any time 00:46.650 --> 00:50.190 that someone goes to my domain name of multik 00:50.190 --> 00:52.890 or keightsmulti.com, they get forwarded 00:52.890 --> 00:55.890 to the IP address that is specified right here. 00:55.890 --> 00:57.720 The second rule that I'm going to set up is going 00:57.720 --> 00:59.370 to make sure that if someone goes 00:59.370 --> 01:03.480 to www.keights-multi.com, they go 01:03.480 --> 01:05.910 to the same IP address as well. 01:05.910 --> 01:07.500 Remember, there is a difference 01:07.500 --> 01:12.270 between, say, www.google.com and just google.com. 01:12.270 --> 01:13.530 And we need to make sure that we handle 01:13.530 --> 01:15.063 both cases appropriately. 01:15.960 --> 01:19.260 All right, so under Custom Resource Records I'm gonna put 01:19.260 --> 01:21.840 a @ symbol in here like so. 01:21.840 --> 01:22.680 I'm then going to make sure 01:22.680 --> 01:25.470 that the A record type is selected. 01:25.470 --> 01:28.380 I'll put in a one hour time-to-live, 01:28.380 --> 01:29.640 which is the, essentially, description 01:29.640 --> 01:31.950 of how long it's gonna take for this new record 01:31.950 --> 01:33.420 to kick into effect. 01:33.420 --> 01:36.660 And then we'll enter in an IP address over here. 01:36.660 --> 01:39.210 The IP address is going to be the IP 01:39.210 --> 01:41.460 that was assigned to your load balancer. 01:41.460 --> 01:42.840 And again, you can find this by going 01:42.840 --> 01:44.580 to the Google Cloud platform 01:44.580 --> 01:47.160 and looking at the Services tab. 01:47.160 --> 01:52.160 So my IP address is 35.224.40.71. 01:52.170 --> 01:54.450 We do not need to add on the port at the end, 01:54.450 --> 01:56.913 we need just the IP address by itself. 01:58.920 --> 02:00.780 So I'll put in the IP like so. 02:00.780 --> 02:03.240 Now, again, notice that there is no colon AD 02:03.240 --> 02:04.770 on here or anything like that. 02:04.770 --> 02:06.603 It's just the IP address. 02:07.696 --> 02:09.546 Okay, so I'm going to add that record 02:10.500 --> 02:13.140 and then we'll create one other record as well. 02:13.140 --> 02:15.150 I'm gonna change the type in this dropdown 02:15.150 --> 02:17.490 to a CNAME record. 02:17.490 --> 02:21.270 I'll put in www on the left-hand side over here. 02:21.270 --> 02:24.210 We'll, again, do a one hour time-to-live. 02:24.210 --> 02:26.010 And then for the domain name, we're going 02:26.010 --> 02:29.040 to make sure that if someone visits the www address, 02:29.040 --> 02:33.240 it's going to send them to keights-multi.com. 02:33.240 --> 02:35.880 And, of course, this will be your particular domain name, 02:35.880 --> 02:37.350 not mine. 02:37.350 --> 02:40.260 So once we get that in there, I'll then click on Add. 02:40.260 --> 02:41.093 And that's pretty much it. 02:41.093 --> 02:42.210 We're good to go. 02:42.210 --> 02:43.860 Now, you'll notice that on the right-hand side, 02:43.860 --> 02:46.380 there's a little dot on there that got inserted. 02:46.380 --> 02:47.250 That's totally fine. 02:47.250 --> 02:49.600 You can leave it in there, no issue whatsoever. 02:50.790 --> 02:53.130 All right, so we've now set up our domain name 02:53.130 --> 02:55.620 and we've pointed it to our IP address 02:55.620 --> 02:57.420 that has our load balancer. 02:57.420 --> 03:00.420 After some amount of time, we're going to eventually be able 03:00.420 --> 03:02.520 to go to the domain that you just purchased 03:02.520 --> 03:04.710 and be able to access our application. 03:04.710 --> 03:06.660 Now, you are going to be able to do that even 03:06.660 --> 03:09.930 before we set up all this HTTPS stuff. 03:09.930 --> 03:11.700 You can access the domain appropriately 03:11.700 --> 03:13.740 without going through all the HTTPS setup, 03:13.740 --> 03:15.300 but of course you are still going to see 03:15.300 --> 03:17.700 that red error, not secure message 03:17.700 --> 03:19.770 until we go through that setup. 03:19.770 --> 03:21.450 All right, so let's take a quick pause right here. 03:21.450 --> 03:23.070 We'll come back to the next section and we're going 03:23.070 --> 03:25.950 to continue with starting to set up our Kubernetes cluster 03:25.950 --> 03:28.140 to obtain a TLS certificate. 03:28.140 --> 03:30.593 So a quick pause and I'll see you in just a minute.