WEBVTT 00:00.390 --> 00:01.700 Hi and welcome to this lesson. 00:02.220 --> 00:04.960 Let's get started by having a look inside a home shop. 00:05.310 --> 00:09.050 So let's go ahead and create a new one, some grown up integrated terminal. 00:09.510 --> 00:14.790 I'm going to help create and I'm going to call this chart templating. 00:17.270 --> 00:17.780 Excellent. 00:18.410 --> 00:19.340 Now we've created it. 00:19.550 --> 00:21.770 Let's have a look at what's happening inside. 00:22.340 --> 00:26.990 When we first had a look at this, we said chance is going to be where our dependencies get pulled in. 00:27.590 --> 00:31.250 And when we are pulling Independence's, we'll have another volunteer called Requirements Dot Yamal. 00:31.700 --> 00:33.710 We're going to see that later on in the course. 00:33.710 --> 00:38.660 When we start moving on to Independence's, we're seeing values that Yamal, we know how it works. 00:39.020 --> 00:41.780 We've got charts that Yamal, things such as veni. 00:42.200 --> 00:48.350 We can have a brief description, but also things such as the child version of a version of the application 00:48.350 --> 00:48.890 inside. 00:49.220 --> 00:54.560 One common practice with this is if you have a Jenkins' pipeline, I'm using Jenkins' for this example, 00:54.560 --> 00:57.320 because this has been the most common platform I've worked with. 00:57.320 --> 01:00.080 But you may be using another CCD solution. 01:00.560 --> 01:06.050 When you're building an application and even a release to production, you'll bump up the version if 01:06.050 --> 01:10.810 you want to deploy a new chart notes to upgrade or bump up the chart version. 01:10.820 --> 01:15.080 But the app version itself may remain the same if there's been no code changes or you might want to 01:15.080 --> 01:15.690 increase it. 01:16.520 --> 01:18.230 This is where you would set those details. 01:19.530 --> 01:24.360 Up next, what I want to show you was inside the templates folder, so we've seen how we've used this 01:24.570 --> 01:27.060 more specifically with the deployment and the service. 01:28.010 --> 01:32.060 We haven't touched on a service account in Congress because we're not using it, but let's have a look 01:32.060 --> 01:32.960 at some more files. 01:33.500 --> 01:37.430 We have notes that text, these are also generated. 01:37.580 --> 01:42.770 And if your case if you delete it, you can run a Helme command to recreate this file a test folder. 01:42.770 --> 01:46.670 It includes test run automatically after our home is deployed. 01:47.330 --> 01:52.150 Depending on your environment, it could be seen as useful or not useful if you apply to some very nice 01:52.150 --> 01:56.240 probes and monitoring the alerting you'll see before your deployment was successful or not. 01:56.270 --> 01:58.400 And you may have more comprehensive testing. 01:58.670 --> 02:02.030 See where the testing will go ahead and check the application is working. 02:02.680 --> 02:05.360 Well, one of the big things that we want to cover is this help us file. 02:06.080 --> 02:10.780 The first thing you notice about this is that it has an underscore and underscores in hell. 02:10.910 --> 02:18.170 Let it know this vault doesn't contain any cupidity manifest when otherwise it doesn't contain any cupidity 02:18.200 --> 02:18.700 object. 02:19.190 --> 02:24.200 And as far as I'm concerned, always has inside is templates inside this file. 02:24.710 --> 02:26.950 What we do is we define things. 02:26.960 --> 02:30.910 It's a bit like creating variables if you come from a programming background in here. 02:30.950 --> 02:34.340 What we're creating is variable so we can set some logic behind as well. 02:34.670 --> 02:42.260 So things like here where truncates a name to 63 characters, if we set some Lelong name where we get 02:42.260 --> 02:43.670 things such as the name. 02:44.560 --> 02:49.300 And we also set things like bilabial, so that's why, Manuell, you've been having to assess it, it 02:49.320 --> 02:54.100 also got some logic today, which we're going to cover in a bit, such as if statements and include 02:54.110 --> 02:55.270 statements in defining. 02:55.570 --> 02:57.910 We're going to cover that in more depth very shortly. 02:58.240 --> 02:59.860 Now, not just limited to having one. 03:00.410 --> 03:02.840 I'm going to go a bit off topic here, but this is something I've seen. 03:02.860 --> 03:06.880 It's been done where the client has been underscored in front of all their files. 03:07.060 --> 03:10.960 So deployment ingress, etc. We've turned those into templates. 03:11.290 --> 03:12.010 So we've helme. 03:12.010 --> 03:13.060 It's a bit like inception. 03:13.060 --> 03:14.770 We have a template within a template. 03:15.340 --> 03:16.810 That's essentially what was far less. 03:17.410 --> 03:18.460 And we can have multiple ones. 03:18.460 --> 03:22.690 In a client's case, there was certain things like deployment and for some reason it wanted some sort 03:22.690 --> 03:23.470 of logic in there. 03:23.660 --> 03:28.870 So we said it as a template, but it creates a deployment and we use an include statement and pull it 03:28.870 --> 03:29.280 from there. 03:30.040 --> 03:31.270 That was a bit of a weird case. 03:31.490 --> 03:36.970 The important thing to note with this file here is that the underscore the notes will Telcel. 03:36.970 --> 03:39.420 But look, there's no humanises resource in here. 03:39.640 --> 03:41.200 This is just a template. 03:41.740 --> 03:46.630 So it'll do next is we'll start going through more in depth and having a look at some of these features 03:46.630 --> 03:47.380 and functionalities. 03:47.380 --> 03:52.840 We can add a Bobby in the U.S., you're going to be an absolute master at helm and templating. 03:53.170 --> 03:55.150 I'll look forward to seeing you in the next lesson.