In the last video, we discussed how this singular property right here really needs to be different,
depending upon whether we are on the development or production that cluster.
There are a couple of different ways for handling this.
I'm gonna show you a very simple, straightforward way.
To solve this, we're going to create a couple of additional directories inside sidebar in for a folder.
I'm going to create another folder inside of infra called AIDS Dash Prod.
And then another one called AIDS Dash Death.
The idea here is that we are going to have summit number of manifests or Yamal files split between all
three directories inside of our K Eights directory.
We're going to have a series of manifest files that can be applied to any cluster that we connect to.
So either a production or deployment cluster.
Inside of the AIDS death directory, as you would guess, we're gonna play some config files inside
of here that are only supposed to be applied to a development cluster and an inside of Cades prod are
going to be manifest that are suppose to be applied to a production cluster.
So now I'm going to take my ingress service file and I'm going to move it into the Kate's dev folder.
Because this file, as it stands right now, should be only applied to a development cluster.
I do not want to use this on my production cluster because that will expose or make use of a host of
ticketing def.
Then inside of Kate's broad, I'm going to make a new file, also called Ingress Savi Dot Yamal.
I'm going to copy everything from the existing Ingress service file and pasted over here and now in
theory, we will change this hostname right here to whatever our final domain name is.
We have not yet purchased a domain name for our application, so we don't have anything to change that
to just yet.
But as soon as we do purchase a domain name for our app, we will come back to the broad file right
here and update that most property.
That's it.
We now have these three different directories.
And again, Cates is going to hold everything that as related to any given Cluster B at development
or production.
Devore's for just development and product is very broad.
Now, by just moving these folders around and moving these files around.
Well, we do have to fix up a couple of other things that are making use of these config files.
So first off, we do have to make sure that we open up our scaffold YAML file.
So whenever you run scaffold, we're gonna tell it that in addition to some config files we place inside
that Kades directory.
We also wanted to use some config files that are going to be inside of the K AIt's dev directory.
So I can add in that line right there.
We're also going to go back over to our get hub repository.
We're gonna find the deploy manifest config file that we just put together and we were going to adjust
that command right there and make sure that in addition to applying everything from the case folder,
we also apply everything from the eights prod folder as well.
So I'm going to edit this file.
And I'll put in a little.
And step right here.
You've CDL apply dash f infra slash eights dashboard.
I think that you might possibly be able to put in multiple directories to a dash F reference.
I'm actually not one percent sure.
Now that I'd say it out loud.
So that would actually be a pretty good place to look at the documentation for that.
You might be able to simplify this to just something that looks like that right there.
But again, you might look at the documentation on your own.
All committees file again.
OK.
So now we should be good to go once we buy a domain name.
We're going to come back to that broad ingress service file, update the host.
And that should pretty much be at.
Well, I think that we're just about ready for an actual test run here.
Now, before we do a test run, there's a little bit more setup we have to do specifically around our
cluster.
You might recall that our cluster expect there to be one or two secrets to find, such as the Jason
Webb token key secret.
So we define that a very long time ago and we made use of it inside of our off deployment.
But here it is right here.
Right now, our digital ocean cluster does not have a secret called JWT key.
I think there might be one other secret somewhere inside of here as well.
We have to mainly create inside of our cluster as well.
So once we create those two secrets, one or two secrets will then be able to test out this entire float
and then start to finish things up.