WEBVTT 00:00.360 --> 00:06.030 And this lesson, I'm going to take you through differences between two and Helme three and big change, 00:06.060 --> 00:06.570 is it? 00:06.570 --> 00:08.120 Tiller has been removed. 00:08.520 --> 00:12.930 If you work with him to, then you may be aware the pain of Tiller and if you completely need to help. 00:13.140 --> 00:14.400 Let me take you for it now. 00:14.730 --> 00:17.880 So Tiller is a key component at the helm to see. 00:17.880 --> 00:21.650 What we'd have is a local machine and we'd have the helm client. 00:22.110 --> 00:24.990 So whenever we insert some of helm, we use the helm client. 00:25.710 --> 00:27.060 So we were to deploy a chart. 00:27.060 --> 00:30.070 We might pull it from Chope Museum or Chart Repository. 00:30.480 --> 00:33.150 And again, this is like DOCA images and we are going to cover this later. 00:33.150 --> 00:39.300 And of course, a chart repository is like Docker Hub, where we can store our charts and pull down 00:39.640 --> 00:40.700 and make this clear. 00:40.740 --> 00:42.810 This is on a local machine. 00:44.400 --> 00:50.640 So then talk to the repository and I'm in droves box here, and this is going to represent achievements, 00:50.640 --> 00:51.270 these cluster. 00:52.500 --> 01:01.140 So it creates a home client I talk to, in other words, it was the helm server called Tylor, and what 01:01.290 --> 01:03.860 it would do is it would talk to the Cuban IT API. 01:04.410 --> 01:06.950 She may be wondering why now I'm free. 01:06.960 --> 01:08.890 And that's the version we're going to use throughout this course. 01:09.360 --> 01:11.730 Why did they remove Teyla and problem? 01:12.480 --> 01:14.000 Is it sometimes it could fall over? 01:14.220 --> 01:17.580 So we've been talking about the helm client being on a local machine. 01:18.000 --> 01:23.100 We could even put this on a jenkins' server so you could automate your entire deployment pipeline by 01:23.100 --> 01:25.170 having a jenkins' job until your deployments. 01:25.170 --> 01:28.620 And then if Scylla went down, that meant you can deploy anything. 01:28.650 --> 01:34.560 But what it also did was keep track of all the changes if we deployed a new version or took an old version 01:34.560 --> 01:39.180 of a shot, but we deployed out all go for it until it would keep track of it. 01:39.690 --> 01:44.010 And with this, the reason it would fall over is it would consume or need more resources. 01:44.260 --> 01:49.460 One of the clients I used to work with was using Helme and Teyla would frequently go out. 01:49.680 --> 01:54.240 So that meant none of the teams across any other projects were able to deploy anything because they 01:54.240 --> 01:54.990 needed Teyla. 01:55.170 --> 01:56.520 And that's what really sparked the movement. 01:56.540 --> 02:01.560 So Subversion three, which is essentially this model without it, and I'll draw it out again. 02:01.980 --> 02:05.860 But this is the big change in Helm too, versus Helm Ferry. 02:06.000 --> 02:07.620 So now let's have a look at helm. 02:07.620 --> 02:14.520 Very so said Helm three is the same as Helm wish to set up except Helm client. 02:15.460 --> 02:22.270 Now, that really talks to the Cubans, this API and Cuba will keep track of any changes that did it 02:22.270 --> 02:25.120 by default anyway, was also there to help the Helmholtz. 02:25.360 --> 02:30.490 So now if we make a change to our deployment, Cubans will be aware of what's currently deployed and 02:30.490 --> 02:33.850 the change we want to make and then we'll go ahead and make that change. 02:34.330 --> 02:37.780 I'll also include a link, include some of the more subtle changes and held version free. 02:38.170 --> 02:41.230 But this is the big one that Tela is no longer used. 02:41.620 --> 02:45.670 And again, the big reason why it was such a problem is it would keep needing more resources because 02:45.670 --> 02:47.020 it was keeping track of so much. 02:47.020 --> 02:49.450 And if it went down battement, you can deploy anything. 02:49.780 --> 02:51.640 So now we've been for what helmet's. 02:51.880 --> 02:54.430 We now know how it works from an architectural point of view. 02:54.610 --> 02:58.150 We're now ready to get started installing it and getting it on our machines. 02:58.510 --> 03:00.550 I'll see in those lessons very shortly.