1 00:00:00,880 --> 00:00:03,650 The last thing we have to do is update or even less once again. 2 00:00:03,650 --> 00:00:07,740 So we're going to update some your Ls inside there to reach out to our newly created comments Curry 3 00:00:07,770 --> 00:00:13,430 and moderation cluster IP services will then rebuild that image push it off to Docker Hub and then update 4 00:00:13,460 --> 00:00:16,130 our deployment to get started. 5 00:00:16,130 --> 00:00:23,120 I'll open up my editor inside of hearing and to find the event plus indexed not just file but here's 6 00:00:23,120 --> 00:00:30,310 where we had just come to it out those recalls so remember we no longer have any kind of idea of local 7 00:00:30,310 --> 00:00:30,820 host. 8 00:00:30,820 --> 00:00:36,050 Instead we have to reach out to the direct cluster IP services if we ever forget the names of those 9 00:00:36,160 --> 00:00:43,080 IP services and all we have to do is go to our terminal and do a QC tell get services do we need to 10 00:00:43,080 --> 00:00:49,470 make sure that we make a request up to comments SRB at port four thousand one moderation at four thousand 11 00:00:49,470 --> 00:00:52,290 three and query at four thousand two 12 00:00:55,530 --> 00:01:01,920 tobacco over here here is four thousand one that should be our comments SRB. 13 00:01:02,000 --> 00:01:16,160 Next up at four thousand and two is query SRB and then finally at four thousand and three is moderation. 14 00:01:16,210 --> 00:01:25,480 All right I'll say this file will then go back over to our terminal let's change into our event bus 15 00:01:25,480 --> 00:01:32,040 directory We're gonna rebuild this image because we made a change to our code though docker build target 16 00:01:34,170 --> 00:01:35,660 don't forget the dot on the very end 17 00:01:39,010 --> 00:01:40,360 well then do a docker push 18 00:01:45,020 --> 00:01:51,220 and then finally don't forget option number two for updating a deployment we'll run cube Seitel rollout 19 00:01:51,240 --> 00:01:56,640 restart deployment and then the deployments name and we have to do that after we successfully push that 20 00:01:56,640 --> 00:02:03,450 image off to Docker Hub so we can do a cube CTO night forget this command all the darn time rollout 21 00:02:03,490 --> 00:02:09,320 restart deployment you think I could remember that rollout restart deployments and the name of our deployment 22 00:02:09,320 --> 00:02:19,810 in this case let's just do a get deployments as a reminder the name of our deployment is where is it 23 00:02:19,820 --> 00:02:20,720 event bus depot. 24 00:02:21,050 --> 00:02:22,460 So Cube CTO 25 00:02:25,170 --> 00:02:34,930 rollout restart deployment event bus depot right after that we can do a get pods and make sure that 26 00:02:34,930 --> 00:02:38,560 the pod was updated so there's the old pod free vent bus. 27 00:02:38,560 --> 00:02:41,980 It's been terminated and here's the new one that was just created with the new image 28 00:02:45,860 --> 00:02:52,020 I can then run pods again and I'll see that the terminated one has now been completely cleaned up and 29 00:02:52,020 --> 00:02:58,000 now we've got just the new version of our code right there inside of event bus all right. 30 00:02:58,060 --> 00:02:59,650 Now how are we going to test this out. 31 00:02:59,650 --> 00:03:02,920 Well we don't really have the react project wired up at all right now. 32 00:03:02,950 --> 00:03:06,450 It's a matter of fact we haven't really discussed the react application whatsoever. 33 00:03:06,460 --> 00:03:11,350 We'll figure that out in just a moment but right now a more immediate test we can do is once again use 34 00:03:11,350 --> 00:03:18,090 postmen to make a new post directly we can then take a look at some logs around say comments or maybe 35 00:03:18,090 --> 00:03:24,720 query moderation just print out some logs and verify make sure that we see some events being received 36 00:03:24,780 --> 00:03:26,040 from the event bus. 37 00:03:26,040 --> 00:03:27,910 I think that's a good enough test for right now. 38 00:03:29,820 --> 00:03:33,050 So let's open up post man once again. 39 00:03:33,090 --> 00:03:36,040 I still got the exact same request loaded up right here. 40 00:03:36,060 --> 00:03:38,450 Remember it is a post to a local host. 41 00:03:38,460 --> 00:03:42,750 If you're on Docker for Windows or Docker for Mac otherwise you'll do that mini cube IP. 42 00:03:42,750 --> 00:03:46,960 You'll then have your node port Port right there which very likely is not. 43 00:03:46,980 --> 00:03:50,030 For a two for you flash posts. 44 00:03:50,070 --> 00:03:53,400 Make sure you've got headers of content type application Jason. 45 00:03:53,550 --> 00:04:01,740 Select raw select Jason and then put in an object or some Jason data like some will then send this looks 46 00:04:01,740 --> 00:04:03,080 like this was successful. 47 00:04:03,130 --> 00:04:10,380 So now we can go and check out some logs back over here remember to retrieve logs. 48 00:04:10,380 --> 00:04:15,090 We're going to do a cube Seitel logs and then the name of the pod that we want to get the logs from. 49 00:04:15,090 --> 00:04:17,470 So let's take a look at the common spot first. 50 00:04:17,670 --> 00:04:27,070 I'll do a cube tell it or something logs based and I can see event received of created. 51 00:04:27,270 --> 00:04:28,610 I'll do the same thing for moderation. 52 00:04:28,620 --> 00:04:32,270 I don't recall if our moderation actually has a console log when it receives an event. 53 00:04:32,310 --> 00:04:37,840 So if we don't see one when we get logs from that thing I'll probably assume that everything is OK right 54 00:04:37,840 --> 00:04:40,640 now at least OK. 55 00:04:40,700 --> 00:04:42,070 So I don't see a log right here. 56 00:04:42,080 --> 00:04:46,370 But again I believe that's because we did not add in any logging whenever we receive any event. 57 00:04:46,370 --> 00:04:49,160 So I'm just going to ignore that right now. 58 00:04:49,160 --> 00:04:56,910 And then finally we'll take a look at query though cubes GTL logs and this one is seeing the event as 59 00:04:56,910 --> 00:04:57,960 well. 60 00:04:57,960 --> 00:04:59,030 Awesome. 61 00:04:59,070 --> 00:05:03,030 Well I think that means that all of our different micro services are loaded into the cluster and they 62 00:05:03,030 --> 00:05:08,160 have the ability to communicate with each other maybe not the moderation one but again I'm pretty sure 63 00:05:08,160 --> 00:05:09,140 that's working just fine. 64 00:05:10,470 --> 00:05:12,140 So we're still not done yet. 65 00:05:12,150 --> 00:05:16,020 Believe it or not even though we've been going through this Cooper Nettie stuff for a really long time 66 00:05:16,560 --> 00:05:22,170 the relaxing lasting do is really figure out that react application there's gonna be some special concerns 67 00:05:22,200 --> 00:05:23,100 around it. 68 00:05:23,100 --> 00:05:24,270 So let's take a pause right here. 69 00:05:24,270 --> 00:05:28,890 We'll come back the next video and discuss how we're going to wire up the react app to all these different 70 00:05:28,890 --> 00:05:29,520 services.