1 00:00:00,470 --> 00:00:04,160 This is the solution video for the core DNS lab. 2 00:00:05,150 --> 00:00:09,290 So for the first question, identified a solution implemented in the cluster. 3 00:00:11,050 --> 00:00:15,070 So let's go to the Domhnall and I still get. 4 00:00:16,780 --> 00:00:19,480 Deployment in the tube system namespace. 5 00:00:22,080 --> 00:00:26,910 And here we have a department called DNS, but two parts. 6 00:00:29,030 --> 00:00:31,760 So select gaudiness as the answer. 7 00:00:33,860 --> 00:00:36,720 How many parts of the DNA server are deployed? 8 00:00:36,740 --> 00:00:39,690 So we already saw that it's two out of two ports which are ready. 9 00:00:39,710 --> 00:00:40,760 So the answer is to. 10 00:00:44,730 --> 00:00:48,060 What is the name of this service created for accessing Codina? 11 00:00:48,130 --> 00:00:53,520 So let's go back to the DOMHNALL and check the service to the same thing as before, but we'll just 12 00:00:53,520 --> 00:00:58,050 look up service and hear the name is Kube Dash DNS. 13 00:01:01,550 --> 00:01:08,150 What is the type of decoding and server that should be configured on postal services so we can just 14 00:01:08,150 --> 00:01:11,230 look up at the IP address of the code in service? 15 00:01:12,050 --> 00:01:18,080 So let's go back and see the same command and the cluster IP here is 10 or 96 dot zero 10. 16 00:01:19,640 --> 00:01:23,900 There is the configuration file located for configuring decoding a service. 17 00:01:27,590 --> 00:01:30,230 So let's inspect the accordionists deployment. 18 00:01:34,520 --> 00:01:38,690 So in this case, I'm going to run cutesie to describe deployment's go DNS. 19 00:01:42,000 --> 00:01:43,470 The system namespace. 20 00:01:45,050 --> 00:01:52,580 And look, let's look up at the comments and arguments for this deployment, for the continued running 21 00:01:52,580 --> 00:01:59,540 on this deployment, and here we can see that the configuration file uses Itzik or DNS or file. 22 00:02:04,820 --> 00:02:11,060 How is the court file past and to the court in a sport, again, we can look up at the configuration 23 00:02:11,060 --> 00:02:18,800 for the deployment and here if you see the configuration file is located at ETEK DNS. 24 00:02:19,220 --> 00:02:26,060 And if you observe underneath, we have a mode called ATC Code DNS, which is from a config volume, 25 00:02:26,240 --> 00:02:28,160 which is of type config map. 26 00:02:29,320 --> 00:02:36,940 So it's basically mounting a conflict map on that part cadenas, and that's the way it is loading this 27 00:02:36,940 --> 00:02:39,760 file when the pod starts up. 28 00:02:39,790 --> 00:02:43,980 So the answer is configured as a conflict map object. 29 00:02:47,260 --> 00:02:53,230 What is the name of the conflict map object created for the CORFO that is called DNS? 30 00:02:56,080 --> 00:03:02,760 What is the root domain zone configured for this group when it is cluster to identify those people, 31 00:03:03,310 --> 00:03:06,940 explore the code in this? 32 00:03:09,800 --> 00:03:10,550 Conflict map. 33 00:03:12,510 --> 00:03:17,820 So let's run cutesie to describe s.m, which is short for conflict map and accordionists conflict, 34 00:03:17,820 --> 00:03:26,310 Mabern here under this file, the core file, we can see that the cluster domain uses cluster or local. 35 00:03:29,580 --> 00:03:30,450 So that's here. 36 00:03:30,480 --> 00:03:32,610 So the answer should be clustered local. 37 00:03:33,730 --> 00:03:40,000 We have deployed a set of pods and services and the default and petroleum species inspect them and go 38 00:03:40,000 --> 00:03:41,080 to the next question. 39 00:03:42,090 --> 00:03:49,360 So first, let's inspect the ports and deployments on all the spaces, specifically default and payroll. 40 00:03:49,380 --> 00:03:53,040 So let's try to get ports. 41 00:03:53,340 --> 00:03:55,230 So that's on the default namespace. 42 00:03:55,230 --> 00:03:58,980 And we can see that we have a few ports by the name of H.R. Test. 43 00:03:59,340 --> 00:03:59,820 Simple. 44 00:03:59,910 --> 00:04:01,650 We have one simple one. 45 00:04:02,430 --> 00:04:03,540 Now let's do the same. 46 00:04:03,990 --> 00:04:04,890 But in the. 47 00:04:06,850 --> 00:04:09,400 Payroll namespace, and here we have. 48 00:04:10,760 --> 00:04:11,840 Port called VEB. 49 00:04:14,130 --> 00:04:16,530 Let's move on to the next question. 50 00:04:20,400 --> 00:04:26,820 What name can be used to access the HRR Web server from the test application, you can execute a command 51 00:04:26,820 --> 00:04:33,450 on the test for the test or we can make use of the application UI, which is located on top of it. 52 00:04:34,110 --> 00:04:40,380 So we know from the previous command that both H.R. and Test are in the same namespace, which is the 53 00:04:40,380 --> 00:04:41,380 default namespace. 54 00:04:41,880 --> 00:04:47,850 So for them to reach each other or using a service name, they do not have to specify the fully qualified 55 00:04:47,850 --> 00:04:51,140 domain name or the name of the namespace. 56 00:04:51,750 --> 00:04:57,990 So we see that there is a service by the name of Web service and the default namespace. 57 00:05:03,000 --> 00:05:10,230 So let's first establish the fact that the Web service does belong to the port called H.R.. 58 00:05:11,370 --> 00:05:15,150 To do that, we will inspect the labels and selectors on the service. 59 00:05:16,530 --> 00:05:22,380 First, let's try still describe as we see the observers and here we can see that the selectors name 60 00:05:22,380 --> 00:05:23,790 is equal to HRR. 61 00:05:25,240 --> 00:05:30,430 Next, let's validate that the same label is used by the port. 62 00:05:33,980 --> 00:05:36,230 So, Ron, you get part. 63 00:05:38,790 --> 00:05:41,100 H.R. Anshul labels. 64 00:05:49,060 --> 00:05:54,310 And here we can see that it matches the Selecter used for the Web service. 65 00:05:56,380 --> 00:06:05,230 So to access this application, we can try to access Web service from the test application, so let's 66 00:06:05,230 --> 00:06:05,900 do that now. 67 00:06:06,760 --> 00:06:10,690 So let's copy paste the name of the service, which is Web service. 68 00:06:13,140 --> 00:06:20,370 And here we can see that the port uses 80, so let's try to resolve it and see if the connectivity from 69 00:06:20,370 --> 00:06:21,640 the test application works. 70 00:06:22,260 --> 00:06:23,940 So the whole thing should be Web service. 71 00:06:24,970 --> 00:06:31,060 And they put it in here, we get the result, saying that this is the server, so it's working well 72 00:06:31,390 --> 00:06:38,680 so we can use Web service as the name to resolve which of these names cannot be used to access the service 73 00:06:38,680 --> 00:06:40,030 from the test port. 74 00:06:40,660 --> 00:06:42,730 So all of these options are correct. 75 00:06:42,730 --> 00:06:44,170 We can use Web service. 76 00:06:44,170 --> 00:06:45,580 We can use Web service. 77 00:06:45,590 --> 00:06:48,480 DOT default, which will default, is the namespace. 78 00:06:48,850 --> 00:06:54,250 We can also use Web service, dot default, dot, SBC, because it's a service. 79 00:06:54,700 --> 00:06:57,520 The only name we cannot use is web service. 80 00:06:57,520 --> 00:06:58,690 Dot default dot part. 81 00:07:01,250 --> 00:07:06,470 Which of the balloon name can be used to access the payroll service from the test application so we 82 00:07:06,470 --> 00:07:15,200 know that the payroll service is not in default namespace and the test application is so to access the 83 00:07:15,200 --> 00:07:19,990 Web service on payroll application will have to up in the name of the namespace. 84 00:07:20,660 --> 00:07:21,830 But let's test that. 85 00:07:22,190 --> 00:07:24,020 So let's add that payroll. 86 00:07:25,670 --> 00:07:27,540 And see the result. 87 00:07:27,560 --> 00:07:33,350 So this does show you that it is able to connect to the payroll server, so the answer is Web service, 88 00:07:33,350 --> 00:07:34,330 DOT payroll. 89 00:07:39,400 --> 00:07:45,370 Which of the blue name cannot be used to access the payroll service from the test application? 90 00:07:47,150 --> 00:07:55,100 So here we can use all of the names to access the service in the payroll namespace, but will notice 91 00:07:55,100 --> 00:07:55,910 that one of them. 92 00:07:57,020 --> 00:08:06,410 Has the value of Web service, payroll, NVC dot cluster, which is not the complete fully qualified 93 00:08:06,410 --> 00:08:09,390 domain name the domain as cluster dot local. 94 00:08:09,920 --> 00:08:13,180 So we cannot connect to it just as we see dot cluster. 95 00:08:13,190 --> 00:08:14,150 So let's test that now. 96 00:08:14,150 --> 00:08:15,380 And you see that it fails. 97 00:08:16,010 --> 00:08:18,080 But if we append cluster dot local. 98 00:08:19,060 --> 00:08:24,980 Which includes the full domain, it would work, but we can also use other options, such as payroll 99 00:08:25,000 --> 00:08:27,310 or SBC or just payroll. 100 00:08:30,790 --> 00:08:38,620 So the incorrect option here is as we see the cluster, we just deployed a Web server called Webapp 101 00:08:38,620 --> 00:08:41,200 that accesses a database called MySQL. 102 00:08:41,800 --> 00:08:47,040 However, the Web server is failing to connect to the database server, troubleshoot and fix the issue. 103 00:08:47,050 --> 00:08:48,220 They could be in different names. 104 00:08:48,580 --> 00:08:55,690 So, yeah, let's first try to find out the names faces that these pods and deployments are on. 105 00:08:58,430 --> 00:09:00,050 So let's go to the Domhnall. 106 00:09:02,710 --> 00:09:11,650 And first, let's run, you get parts, all news pieces, so this will show up any new polls that have 107 00:09:11,650 --> 00:09:14,080 been created and different namespace. 108 00:09:14,110 --> 00:09:20,350 So we see that there is a port by the name of my sequel's, which is now in the payroll part, the payroll 109 00:09:20,350 --> 00:09:20,980 namespace. 110 00:09:21,550 --> 00:09:23,230 And there is a new port. 111 00:09:23,230 --> 00:09:25,060 And the default names is what it looks like. 112 00:09:25,060 --> 00:09:30,160 It's a deployment just by looking at the name so that as of a deployment. 113 00:09:30,160 --> 00:09:31,120 So let's run Cuba. 114 00:09:31,360 --> 00:09:33,130 You get deployment's. 115 00:09:34,200 --> 00:09:40,050 And the only space and here we have a webapp deployment which was created a few moments ago. 116 00:09:42,620 --> 00:09:49,550 And in the payroll namespace, that the MySQL part, which the webapp deployment is trying to connect 117 00:09:49,550 --> 00:09:49,820 to. 118 00:09:51,760 --> 00:09:58,180 So let's open the Web server and we see that the Web page shows a failed result and here we have environment 119 00:09:58,180 --> 00:09:58,630 variables. 120 00:09:58,630 --> 00:10:05,200 DB holes is equal to my school, so it is not trying to connect to the payroll namespace in this case. 121 00:10:05,200 --> 00:10:08,170 It's trying to look for MySQL and the default space. 122 00:10:08,170 --> 00:10:10,300 And because it does not exist, it feels. 123 00:10:12,540 --> 00:10:20,190 So let's edit our deployment, and for that, we will face the definition file for the webapp deployment 124 00:10:20,940 --> 00:10:23,700 using Kubek to get deployments. 125 00:10:23,700 --> 00:10:26,250 Web app Dash Oyamel. 126 00:10:28,190 --> 00:10:30,150 And will be redirected to. 127 00:10:33,150 --> 00:10:40,380 Once that is done, let's open it up using the editor and navigate to the environment section. 128 00:10:41,930 --> 00:10:50,480 And on the environment, we will change the value for DBI underscore host to Michael Dot payroll because 129 00:10:50,480 --> 00:10:54,800 this service resides on the payroll namespace. 130 00:10:55,800 --> 00:11:02,880 Once this is done, we can save and exit this file and we can still apply to update the pod on this 131 00:11:02,880 --> 00:11:03,510 deployment. 132 00:11:06,500 --> 00:11:13,040 But just to validate, we see that the service called my school is in payroll namespace and now we can 133 00:11:13,040 --> 00:11:13,700 create. 134 00:11:15,290 --> 00:11:16,160 New deployment. 135 00:11:21,210 --> 00:11:27,410 So let's try and apply the EFF Web app demo so they should recreate the pod. 136 00:11:28,250 --> 00:11:31,170 Don't need the old pod and create a new one and it's please. 137 00:11:32,920 --> 00:11:35,170 With the updated environment variable. 138 00:11:36,750 --> 00:11:43,380 So now to validate because the partisan is running said, let us check the Web application. 139 00:11:45,680 --> 00:11:49,640 Let's refresh it and now you see that it's working as expected. 140 00:11:54,440 --> 00:12:01,550 For the last question from the airport, and that's been my Secret Service and they the output to a 141 00:12:01,560 --> 00:12:06,420 fire, so we know that they are partners in the defining space. 142 00:12:06,420 --> 00:12:09,890 So we'll use cubicle exec command and. 143 00:12:11,040 --> 00:12:14,520 This case will use Dash, Dash and let's look up and let's test if. 144 00:12:15,700 --> 00:12:20,380 We can run and look up with just the name Michael. 145 00:12:21,500 --> 00:12:26,150 Which should fail because there is no service by that name in the default namespace, but let's try 146 00:12:26,150 --> 00:12:26,710 that anyway. 147 00:12:27,830 --> 00:12:33,680 As you can see, it's failing, but let's add my school payroll and it should resolve the IP address 148 00:12:33,680 --> 00:12:34,400 of the service. 149 00:12:34,430 --> 00:12:37,940 So now let's redirect this to the file, which is Slashdot. 150 00:12:37,940 --> 00:12:39,180 And it's like a.. 151 00:12:39,200 --> 00:12:39,530 Look up. 152 00:12:39,530 --> 00:12:40,190 Dot out. 153 00:12:43,660 --> 00:12:46,360 And that should be it, let's validate. 154 00:12:50,230 --> 00:12:51,450 So the fire looks correct. 155 00:12:53,090 --> 00:12:55,560 And our answer is correct as well. 156 00:12:56,500 --> 00:12:57,710 So that was the last question. 157 00:12:57,730 --> 00:13:00,150 Thank you for joining me in this solution. 158 00:13:00,160 --> 00:13:00,550 We do. 159 00:13:00,580 --> 00:13:01,810 I'll see you in the next one.