1 00:00:01,940 --> 00:00:02,150 All right. 2 00:00:02,180 --> 00:00:04,340 Time to test out the final test here. 3 00:00:04,430 --> 00:00:08,990 We're going to make sure that we can make a change to all five of the services besides off. 4 00:00:09,550 --> 00:00:14,840 And if we commit those changes, make a PR merge in the PR, we should see all five these additional 5 00:00:14,840 --> 00:00:16,820 services be updated inside of our cluster. 6 00:00:17,510 --> 00:00:22,790 So we're going to essentially go through client expiration orders, payments and tickets, and we're 7 00:00:22,790 --> 00:00:25,310 going to make one small, arbitrary change to each of them. 8 00:00:25,940 --> 00:00:29,000 Let's start off first with client and side of client. 9 00:00:29,270 --> 00:00:32,330 Let's change about on pages. 10 00:00:32,930 --> 00:00:33,830 Index J.S.. 11 00:00:36,970 --> 00:00:38,530 About onto each one right here. 12 00:00:39,250 --> 00:00:40,780 Let's just change that to an H to. 13 00:00:42,240 --> 00:00:43,800 So just a small, arbitrary change. 14 00:00:45,680 --> 00:00:46,990 So that's one change down. 15 00:00:47,390 --> 00:00:50,450 Next, I'm going to go to expiration inside of expiration. 16 00:00:50,480 --> 00:00:51,750 I'm going to open up the index. 17 00:00:51,820 --> 00:00:52,040 Yes. 18 00:00:52,040 --> 00:00:53,780 File very similar to the others. 19 00:00:53,810 --> 00:00:55,460 Let's out in a little console log. 20 00:00:57,530 --> 00:00:59,120 At the very top of these start function. 21 00:01:02,530 --> 00:01:04,740 Kate, there's a change to our expiration service. 22 00:01:05,900 --> 00:01:09,470 Then inside of orders, inside the index, not to us file. 23 00:01:10,100 --> 00:01:13,550 Add in another couple of dots to the starting message that we had already added in. 24 00:01:17,840 --> 00:01:18,820 Inside of payments. 25 00:01:20,040 --> 00:01:23,220 Let's open the index out to yes, file, very similar to the others. 26 00:01:23,490 --> 00:01:24,810 Let in a little starting. 27 00:01:25,970 --> 00:01:26,950 Bounce a log at the top. 28 00:01:31,120 --> 00:01:32,840 And then finally inside of tickets. 29 00:01:33,730 --> 00:01:35,230 Open up our index, not to us file. 30 00:01:35,830 --> 00:01:36,300 You guessed it. 31 00:01:36,310 --> 00:01:36,850 Same thing. 32 00:01:37,840 --> 00:01:38,920 A little starting. 33 00:01:42,780 --> 00:01:42,950 OK. 34 00:01:43,020 --> 00:01:46,260 So we now have changes made to five different services. 35 00:01:46,620 --> 00:01:51,420 So we now commit these, create the pull request, merge the request, gets GitHub should detect that 36 00:01:51,420 --> 00:01:53,280 something inside of each of these folders has changed. 37 00:01:53,670 --> 00:01:55,930 And it should run the respective deployment files. 38 00:01:56,930 --> 00:01:58,170 So let's go back over to our terminal. 39 00:01:58,950 --> 00:02:00,930 We're going to change over to our def branch. 40 00:02:03,230 --> 00:02:03,590 We'll see. 41 00:02:03,620 --> 00:02:04,730 All five those changes. 42 00:02:04,760 --> 00:02:06,470 Make sure you've got five changes right here. 43 00:02:08,690 --> 00:02:11,210 We will add all those kimmet them. 44 00:02:14,870 --> 00:02:16,490 And then pushed to our death branch once again. 45 00:02:24,460 --> 00:02:25,630 Then back over on GitHub. 46 00:02:27,630 --> 00:02:28,810 Almost last time we had to do this. 47 00:02:28,830 --> 00:02:29,310 Don't worry. 48 00:02:29,400 --> 00:02:32,100 I know crudities, blurry requests gets kind of tiresome really quickly. 49 00:02:32,490 --> 00:02:34,770 We're going to create a new pull request for the death branch. 50 00:02:34,800 --> 00:02:35,280 Once again. 51 00:02:38,430 --> 00:02:44,280 They'll select Dev and try to merge Dev into master, and I should see the commit that I just made or 52 00:02:44,340 --> 00:02:50,880 really the one commit flushes out changes to client expiration orders, payments and tickets. 53 00:02:52,530 --> 00:02:53,740 They're going to create Despoiler request. 54 00:03:01,640 --> 00:03:04,070 Now, I can run, allow all these tests to run. 55 00:03:04,670 --> 00:03:05,840 I'm just going to hold for a second. 56 00:03:05,870 --> 00:03:07,370 Let these tests run and finish up. 57 00:03:10,930 --> 00:03:12,070 My tests are now complete. 58 00:03:12,130 --> 00:03:13,900 So I'm going to merge the polar request. 59 00:03:18,270 --> 00:03:20,580 All right, so now once again, we can go back up to the top. 60 00:03:20,760 --> 00:03:21,900 Take a look at actions. 61 00:03:23,380 --> 00:03:28,450 Now, we should be able to take a look at our workflows for deploy orders, payments, tickets, expiration 62 00:03:28,480 --> 00:03:31,180 and clients and see that all them have a running job. 63 00:03:31,480 --> 00:03:33,640 Or we can just look at this main display right here as well. 64 00:03:34,300 --> 00:03:39,280 So looks like I'm running a job from client expiration tickets, payments and orders. 65 00:03:40,150 --> 00:03:42,880 Now we can wait for 30 seconds or so once again. 66 00:03:43,240 --> 00:03:45,010 We should see all these jobs go green. 67 00:03:45,370 --> 00:03:48,690 If any of them fail, that means that there's definitely some configuration issue. 68 00:03:49,030 --> 00:03:50,800 And you'll want to take a look at the message. 69 00:03:51,280 --> 00:03:52,240 You can click on the job. 70 00:03:52,270 --> 00:03:54,910 It'll give you some information on why the job failed. 71 00:03:55,370 --> 00:03:59,050 You'll use that as the source to try to debug the thing and figure out what is going on. 72 00:03:59,980 --> 00:04:04,690 Now, if you tried to debug a failing job and you just don't have any idea what's going on and you need 73 00:04:04,690 --> 00:04:06,300 help, I'd be happy to help you. 74 00:04:06,340 --> 00:04:09,040 But you gotta link me to your repository. 75 00:04:09,070 --> 00:04:14,590 I got to see your code to make sure that your repository is public and provide me a link. 76 00:04:14,620 --> 00:04:19,180 You can email it to me or post something in the way and I'll take a look at these failing jobs and hopefully, 77 00:04:19,190 --> 00:04:20,800 Bill, to help you figure out what is going on. 78 00:04:24,850 --> 00:04:28,660 Eventually, all these jobs should go green, which means that hopefully we have successfully built 79 00:04:28,660 --> 00:04:31,420 the images and deployed them off to our communities cluster. 80 00:04:31,830 --> 00:04:33,640 So I'm then going to go back over to my terminal. 81 00:04:33,760 --> 00:04:37,990 We're going to do another get pods and just make sure that we've got some latest versions of all these 82 00:04:37,990 --> 00:04:38,590 images running. 83 00:04:41,540 --> 00:04:41,840 All right. 84 00:04:42,350 --> 00:04:44,570 It looks like I have an ear or two right here. 85 00:04:44,960 --> 00:04:45,250 Sorry. 86 00:04:45,320 --> 00:04:47,390 That pod is still in the process of being deployed. 87 00:04:47,750 --> 00:04:49,670 It looks like everything else is successfully running. 88 00:04:50,540 --> 00:04:56,150 Now, if you have any pods that are persistently airing out, so do give it a minute or two to resolve 89 00:04:56,180 --> 00:04:57,500 and launch all these new pods. 90 00:04:57,740 --> 00:05:00,710 But if after a couple minutes, it looks like everything is still crashing. 91 00:05:01,040 --> 00:05:04,640 I would encourage you to take the name of the pod, let's say the expiration service. 92 00:05:04,670 --> 00:05:10,350 One is crashing and do a QVC T.L. describe pod and then put in the name of the pod. 93 00:05:11,100 --> 00:05:16,070 When you run a command, it will then give you hopefully some reasons on why it is crashing specifically 94 00:05:16,070 --> 00:05:17,270 in the event section down here. 95 00:05:17,930 --> 00:05:21,410 The other thing you can do is pull logs off of a crashing pod. 96 00:05:21,890 --> 00:05:25,610 You can do a QVC T.L. logs and then put the name of the pod in. 97 00:05:27,530 --> 00:05:28,570 There's something like. 98 00:05:30,880 --> 00:05:31,570 Take the name. 99 00:05:34,080 --> 00:05:38,280 But in the name and then you will hopefully see some information right here to help you understand exactly 100 00:05:38,280 --> 00:05:38,970 what is crashing. 101 00:05:40,160 --> 00:05:43,880 All right, so at this point, hopefully, again, after a couple of minutes, you eventually see all 102 00:05:43,880 --> 00:05:45,500 these different prods running successfully. 103 00:05:45,880 --> 00:05:48,380 That means that our application is up and running. 104 00:05:48,500 --> 00:05:49,000 Yay! 105 00:05:49,310 --> 00:05:50,360 That's exactly what we want. 106 00:05:51,320 --> 00:05:53,180 Now, we cannot test this out just yet. 107 00:05:53,270 --> 00:06:00,110 As a reminder, we still do need to get a domain name and register it or assign it to our Ingress Engine 108 00:06:00,140 --> 00:06:00,890 X service. 109 00:06:01,080 --> 00:06:05,180 So we still have a little bit of setup to go through here, but it looks like our cluster is more or 110 00:06:05,180 --> 00:06:05,930 less ready to go.