We are just about ready to do a final test of our deployment process.
But before we do one last little piece of setup, remember, before we make use of ingress, engine
X inside of a cluster, we have to do a little set up command from the Ingress Engine X documentation.
Let's go run that right now.
We're going to execute that command manually against our digital ocean cluster.
So inside of a new browser tab, I'm going to do a search for ingress, engine X.
Going to find the home page for Ingress, Engine X right here.
Well, then find the deployment section.
And then remember, there are many different set commands depending upon how we are running our cluster.
In our case, we are running our cluster on digital ocean language to go to the digital ocean setup
command.
Here it is right here.
I will copy that command.
And then going to go back over to my terminal.
And before I run the command, I'm going to double check and make sure that my cube CTO client is connecting
to my digital ocean cluster.
Remember, you can verify that either by going to doctor for Windows or doctor for Mac.
Taking a look at that Cuban menu dropdown and making sure that you're using your ticketing context.
Alternatively, if you're using mini KUB.
You're going to run those commands of cutesy T.L. config view that will tell you the name of your digital
ocean context.
You can take that name and then run QVC, DL config, use context and then that context name.
So once you're a QVC, TLC instance is configured appropriately.
Well, then pasted that command and run it.
All right.
Looks like everything is being created very good.
So after all that stuff gets created, there is one last quick thing we have to do.
We have made some changes.
To the structure of our infra directory.
So we've got all these changes to where all these different files live right now.
So we need to make sure that we commit these changes and push them up to the master branch.
So when we eventually merge our new code.
Well, we'll pull along these changes with it and we will make sure that we only deploy the appropriate
ingress service file.
So we are going to commit these changes directly to master and push them up, not just, you know,
when we commit to master and push them up.
That is going to cause that works.
That workflow that we just put together, the deployment workflow to run one time.
So as soon as we push these changes up, specifically these split directories right here, that is going
to cause a deployment to our digital ocean cluster.
So we should Emili, after committing these and pushing them manually, we which build to inspect our
cluster and see a bunch of deployments being created and stuff like that.
Let's do that manually right now.
And again, this is one the only times you're going to manually commit to master and push changes to
master.
In general, we are always going to open a pull request instead and use a portal quest to merge and
changes.
OK, so back in the terminal, I'm going to check out M..
I gonna do a get status and just verify.
Yep, I got those two directory changes.
I got some changes to the Scaffold YAML file and I move the Ingress service file, two copies of it
to those two new directories.
Going to add all these changes.
Going to commit them and I'll say split eights manifests.
And then I will push to master.
And I've got some changes up on master once again, my mistake.
Once again, I need to do a poll or G.M. really quickly.
After author, my merge message, and now I can do a push to Origin Master.
All right, there we go.
Now, if we go over to get Hub really quickly.
And take a look at our actions tab.
Once again.
We're going to see if we click on it, deploy manifests and deploy off.
We should see that there are some changes that have now been admitted.
So we should see that split in four directory.
And if we click on that and go to build.
We should see that we successfully install Dactyl, that we apply to all girls olders inside of arcades
and cades pro directories, and that everything was completed successfully.
After we verify that everything was executed successfully, we should then be able to go back over to
our terminal and then get a listing of all the pods running on our digital ocean cluster.
We should be able to do a K or cube CTO.
Get pods and that should run or get a list of all the pods that have been created on our cluster.
Now, you'll notice that in my case, I've got some definite errors here, and that's solely OK.
If you have errors, that is OK as well.
We're going to first get all of our tooling put together and then we'll worry about doing some troubleshooting
here and figuring out exactly what is going on.
All we want to really see right now is that some resources were success or I shouldn't even say successfully
created.
We really just want to see that some pods are attempting to be created.
That's all we want to see right now.
All right, so now that I have verified that my get hub action workflow has tried to push some manifests
off to my cluster.
We're going to take a pause right here.
We can come back the next video.
We're going to test out making a pull request to our auth service and make sure that we can create a
or up play request and see those changes get deployed to our cluster.
Once we go through that workflow at least once, we're then going to do some troubleshooting and figuring
out why some these different pods are failing to be created.