Hi and welcome to this lesson.
Let's get started by having a look inside a home shop.
So let's go ahead and create a new one, some grown up integrated terminal.
I'm going to help create and I'm going to call this chart templating.
Excellent.
Now we've created it.
Let's have a look at what's happening inside.
When we first had a look at this, we said chance is going to be where our dependencies get pulled in.
And when we are pulling Independence's, we'll have another volunteer called Requirements Dot Yamal.
We're going to see that later on in the course.
When we start moving on to Independence's, we're seeing values that Yamal, we know how it works.
We've got charts that Yamal, things such as veni.
We can have a brief description, but also things such as the child version of a version of the application
inside.
One common practice with this is if you have a Jenkins' pipeline, I'm using Jenkins' for this example,
because this has been the most common platform I've worked with.
But you may be using another CCD solution.
When you're building an application and even a release to production, you'll bump up the version if
you want to deploy a new chart notes to upgrade or bump up the chart version.
But the app version itself may remain the same if there's been no code changes or you might want to
increase it.
This is where you would set those details.
Up next, what I want to show you was inside the templates folder, so we've seen how we've used this
more specifically with the deployment and the service.
We haven't touched on a service account in Congress because we're not using it, but let's have a look
at some more files.
We have notes that text, these are also generated.
And if your case if you delete it, you can run a Helme command to recreate this file a test folder.
It includes test run automatically after our home is deployed.
Depending on your environment, it could be seen as useful or not useful if you apply to some very nice
probes and monitoring the alerting you'll see before your deployment was successful or not.
And you may have more comprehensive testing.
See where the testing will go ahead and check the application is working.
Well, one of the big things that we want to cover is this help us file.
The first thing you notice about this is that it has an underscore and underscores in hell.
Let it know this vault doesn't contain any cupidity manifest when otherwise it doesn't contain any cupidity
object.
And as far as I'm concerned, always has inside is templates inside this file.
What we do is we define things.
It's a bit like creating variables if you come from a programming background in here.
What we're creating is variable so we can set some logic behind as well.
So things like here where truncates a name to 63 characters, if we set some Lelong name where we get
things such as the name.
And we also set things like bilabial, so that's why, Manuell, you've been having to assess it, it
also got some logic today, which we're going to cover in a bit, such as if statements and include
statements in defining.
We're going to cover that in more depth very shortly.
Now, not just limited to having one.
I'm going to go a bit off topic here, but this is something I've seen.
It's been done where the client has been underscored in front of all their files.
So deployment ingress, etc. We've turned those into templates.
So we've helme.
It's a bit like inception.
We have a template within a template.
That's essentially what was far less.
And we can have multiple ones.
In a client's case, there was certain things like deployment and for some reason it wanted some sort
of logic in there.
So we said it as a template, but it creates a deployment and we use an include statement and pull it
from there.
That was a bit of a weird case.
The important thing to note with this file here is that the underscore the notes will Telcel.
But look, there's no humanises resource in here.
This is just a template.
So it'll do next is we'll start going through more in depth and having a look at some of these features
and functionalities.
We can add a Bobby in the U.S., you're going to be an absolute master at helm and templating.
I'll look forward to seeing you in the next lesson.