It looks like everything inside of my deployment process went as expected, so I built the image, pushed
off to Docker Hub, restarted the deployment.
And if I go back over to my terminal, I should be able to do a cube CDL get pods I should build to
find the running orthopod right here.
And I'm going to try to pull logs from that pod when I pull logs.
I should see a startup message.
It looks identical to the one we just authored back inside of its indexed, not T.
S file.
Though starting up with about eight dots or so.
So to pull logs from that pod right there, I'm going to do a QVC T.L. logs and then I'll paste in the
name of that pod.
And there we go.
So we've got starting up with the appropriate number of dots, which means we have deployed the latest
version of our service.
Well, this looks pretty fantastic.
Now, the last thing we really have to do here, besides a little bit of networking for ingress in Gen
X, you have to go around to all of our other services and create a very similar deployment file for
them as well.
We'll make this change directly on GitHub.
So we'll just use the built and get hub.
Ed, we're essentially going to duplicate that deployment off file that we had created just a moment
ago to back on GitHub.
I'm going to go to my code tab.
I'm going to find Dodd, get Hubb slash workflows.
I'm going to open up, deploy off dot Yamal.
And then we're going to copy everything inside of your into about five other files in total, I think.
You have to create one for client tickets, payment.
All that stuff.
And you know what?
Now that I mentioned that using the built in GitHub, Ed is prolly can be a little bit of a pain.
So how about instead we just copy this and create some Yamal files inside of our workflows directory
inside of our local ED rather than using the get hub one.
That just means we're going to have to do another push directly to our master branch, which is OK in
this case.
All right.
So I'm going to copy everything we see inside of your well, then go backwards, my terminal.
I want to make sure I check out M..
And just be careful.
I'm going to pull down all the changes once again because I keep trying to push after forgetting to
pull.
Then back inside of our Ed.
We can find that dot get hub workflows directory.
Doonside, if you're going to create a collection of different deploy files or client orders, tickets,
payments and expiration so of workflows, make a new file of deploy dash.
Client thought Yamal.
I'll make another one of deploy orders.
Deploy tickets.
Deploy.
Immense.
And deploy exploration.
All right, so a couple of different files here where you have to go through each one and just paste
in all that stuff that we just copied and make a couple of changes to just a couple of different properties
inside there.
We're pretty much just fixing up the name because you've got a lot of references to off inside the script.
We just need to update those references to whatever we're actually trying to reference.
All right, so back inside.
Let's start with how about our client deployment file?
So deploy client YAML.
I'm going to paste all that stuff that we just copied inside of your.
We're then going to go through and replace every reference to off with client, so client.
Wyant.
Wyant, that's three.
Here is for.
Year five.
And here's six.
So if I do a find inside of here and look for off, I should get no results.
I'm going to say that file and close it.
We'll move on to.
How about expiration next?
So inside of the deploy expiration file, I'm going to do another paste.
We're gonna make sure that we change six instances of off over to expiration.
In this case, I'm going to do a multi select.
There's one, two, three or five and six.
I'm gonna change all six to expiration.
Once again, I should go to do a find inside of here for off and find nothing.
What's next?
We got our orders file the deploy orders, not YAML.
I'll do a Paiste one, two, three, four, five and six.
Change them all over to orders.
Again, do a search for off, make sure I get zero results.
Onto your payments, they'll do a Paiste.
One, two, three, four, five and six over the payments, as usual.
Do a search for art, make sure I got zero results.
Save that and close it.
And we are on to our last one.
The diploid tickets YAML file.
We'll do another Paiste.
One, two, three, four, five and six change them two tickets, and that should be at one more quick
check here.
Just make sure we don't have the word off inside this file.
All right.
So that should be at this point.
This is another location where I can guarantee you a lot of people are going to forget to change the
word off inside of one of these files.
Just I guarantee it.
So it really would be worth your time to double check the deploy files that we just created.
All five of them.
And just double check.
Make sure you do not have the word off inside of any of them.
An easier way to do this would be to do a find on the workflows directory.
So inside the workflows folder, I can do a search for off and I should only find results inside of
deploy off and test off.
All right, Salix, good.
Now, once again, we're going to commit these changes directly to master and push them up.
We can then try to make a change to each of these different services, create a PR for all them dumb,
merge the PR and make sure that all these changes actually get deployed into our cluster.
So back to my terminal.
I'll do it, get status while on the master branch.
I should see the five deployed files we just created.
I'll add all five of them.
And commit them.
And then push off.
Now, again, because we are pushing directly to master our reclose, are going to immediately run for
all five of those different files.
We should see new deployments or jobs running for all five.
But in this case, remember, the one thing to keep in mind as well is that we do have a filter in there
to make sure that we only try to do a deployment or run those workflows.
If something changed inside the respective services.
So actually, on second thought, we probably won't see any deployments running at all at this point.
We actually do have to make a change to all five services and commit them, make the full request,
merge the request to actually trigger a change inside those directories.
And that finally is going to run our actual workflows.
So let's take a pause right here and take a shot at that in the next video.