The last thing we have to do is update or even less once again.
So we're going to update some your Ls inside there to reach out to our newly created comments Curry
and moderation cluster IP services will then rebuild that image push it off to Docker Hub and then update
our deployment to get started.
I'll open up my editor inside of hearing and to find the event plus indexed not just file but here's
where we had just come to it out those recalls so remember we no longer have any kind of idea of local
host.
Instead we have to reach out to the direct cluster IP services if we ever forget the names of those
IP services and all we have to do is go to our terminal and do a QC tell get services do we need to
make sure that we make a request up to comments SRB at port four thousand one moderation at four thousand
three and query at four thousand two
tobacco over here here is four thousand one that should be our comments SRB.
Next up at four thousand and two is query SRB and then finally at four thousand and three is moderation.
All right I'll say this file will then go back over to our terminal let's change into our event bus
directory We're gonna rebuild this image because we made a change to our code though docker build target
don't forget the dot on the very end
well then do a docker push
and then finally don't forget option number two for updating a deployment we'll run cube Seitel rollout
restart deployment and then the deployments name and we have to do that after we successfully push that
image off to Docker Hub so we can do a cube CTO night forget this command all the darn time rollout
restart deployment you think I could remember that rollout restart deployments and the name of our deployment
in this case let's just do a get deployments as a reminder the name of our deployment is where is it
event bus depot.
So Cube CTO
rollout restart deployment event bus depot right after that we can do a get pods and make sure that
the pod was updated so there's the old pod free vent bus.
It's been terminated and here's the new one that was just created with the new image
I can then run pods again and I'll see that the terminated one has now been completely cleaned up and
now we've got just the new version of our code right there inside of event bus all right.
Now how are we going to test this out.
Well we don't really have the react project wired up at all right now.
It's a matter of fact we haven't really discussed the react application whatsoever.
We'll figure that out in just a moment but right now a more immediate test we can do is once again use
postmen to make a new post directly we can then take a look at some logs around say comments or maybe
query moderation just print out some logs and verify make sure that we see some events being received
from the event bus.
I think that's a good enough test for right now.
So let's open up post man once again.
I still got the exact same request loaded up right here.
Remember it is a post to a local host.
If you're on Docker for Windows or Docker for Mac otherwise you'll do that mini cube IP.
You'll then have your node port Port right there which very likely is not.
For a two for you flash posts.
Make sure you've got headers of content type application Jason.
Select raw select Jason and then put in an object or some Jason data like some will then send this looks
like this was successful.
So now we can go and check out some logs back over here remember to retrieve logs.
We're going to do a cube Seitel logs and then the name of the pod that we want to get the logs from.
So let's take a look at the common spot first.
I'll do a cube tell it or something logs based and I can see event received of created.
I'll do the same thing for moderation.
I don't recall if our moderation actually has a console log when it receives an event.
So if we don't see one when we get logs from that thing I'll probably assume that everything is OK right
now at least OK.
So I don't see a log right here.
But again I believe that's because we did not add in any logging whenever we receive any event.
So I'm just going to ignore that right now.
And then finally we'll take a look at query though cubes GTL logs and this one is seeing the event as
well.
Awesome.
Well I think that means that all of our different micro services are loaded into the cluster and they
have the ability to communicate with each other maybe not the moderation one but again I'm pretty sure
that's working just fine.
So we're still not done yet.
Believe it or not even though we've been going through this Cooper Nettie stuff for a really long time
the relaxing lasting do is really figure out that react application there's gonna be some special concerns
around it.
So let's take a pause right here.
We'll come back the next video and discuss how we're going to wire up the react app to all these different
services.