So you can see here we've got values, service, support and values service type.
Now, if we go to our values file, we're also going to clean this up a bit.
But we can see here Values is referring to our values fall.
And we saw that service, which is here, and we saw port, which is going to be set to 80.
So now we have multiple values, let's say in production.
It runs on 80, 80.
I can have a production values for 70, 80, 80 in the values vault and pass that in as a separate one.
And that's something we'll cover a bit later.
Using multiple values falls.
But this is where templating happens.
Sort of values fall is a standard YAML file.
So let's go ahead and start stripping some of this stuff out.
So you want to keep in effect is our service and a deployment.
So this is going to be a very barebones deployment.
So personal preference when I'm creating an object incumbencies, I like to have separated.
So what we've done here would be service.
We have service and any options available.
In my case, I'm going to put in deployment Kotal and I'm going to indents the image and the repository
will do little to bring in the account.
Set about here.
Rechange repository, so we could put down here this version as well.
So that's the latest.
It's got a cluster opaque, so we'll change it to no port.
We also need to set the name, the name to helm deployment.
And we have an name here to help service.
Now we set our values in the fall.
Let's go ahead and use it.
So we'll start with a service.
It's much smaller.
And again, following this format, it's going to be Kobe Bryant.
Kobe Bryant.
I put two spaces in and then dalts values.
Those service Dutney.
And to recap what this is going to do is reference a values fall, isn't going to go for it, go to
service and the value of name.
That's what it's going to use when we actually deploy this service is going to be called Helme service.
If you need to add, here is the node port service to thirty one thousand two hundred thirty four target
port.
That's eighty.
And the port, as we've seen in the values file, is set to eight years, will bring things like this
we can set.
So what do we have to go do that as well?
So target Paul.
I will no, Paul.
So it's over now, values service, top nopal.
The same target also values the service that target poor with no service.
Let's jump into the deployment next.
And this has changed values, dots, and we need to put a deployment account because we see in the values
fall, this deployment don't count.
The name is it referencing from the help of our Serevent and Walkaways Ingenix container.
And this is called an interesting user notice and double quotes, but is not another double quaternion
like this.
Leaving it this way is perfectly valid.
And what Helen will do is when it goes to deploy, you will actually interpolate or replace the values
inside with double quotes.
So let's double check our values file.
So your image app and version.
So let's say it can be values, double deployment dot image.
Dots, and we said it's going to be up and we need to do hit extraversion, so double calibrates.
The values talk, deployment, dot image, dot version, and lastly, in our deployment, we need to
add the name, so we'll do that with culebras, culebras, dot values.
Dot deployment, dot name.
And we'll confirm that now values that Yamal so-called values, dot deployment, dot name perfect.
Now, let's go ahead and deploy our chart.