And this lesson, I'm going to take you through differences between two and Helme three and big change,
is it?
Tiller has been removed.
If you work with him to, then you may be aware the pain of Tiller and if you completely need to help.
Let me take you for it now.
So Tiller is a key component at the helm to see.
What we'd have is a local machine and we'd have the helm client.
So whenever we insert some of helm, we use the helm client.
So we were to deploy a chart.
We might pull it from Chope Museum or Chart Repository.
And again, this is like DOCA images and we are going to cover this later.
And of course, a chart repository is like Docker Hub, where we can store our charts and pull down
and make this clear.
This is on a local machine.
So then talk to the repository and I'm in droves box here, and this is going to represent achievements,
these cluster.
So it creates a home client I talk to, in other words, it was the helm server called Tylor, and what
it would do is it would talk to the Cuban IT API.
She may be wondering why now I'm free.
And that's the version we're going to use throughout this course.
Why did they remove Teyla and problem?
Is it sometimes it could fall over?
So we've been talking about the helm client being on a local machine.
We could even put this on a jenkins' server so you could automate your entire deployment pipeline by
having a jenkins' job until your deployments.
And then if Scylla went down, that meant you can deploy anything.
But what it also did was keep track of all the changes if we deployed a new version or took an old version
of a shot, but we deployed out all go for it until it would keep track of it.
And with this, the reason it would fall over is it would consume or need more resources.
One of the clients I used to work with was using Helme and Teyla would frequently go out.
So that meant none of the teams across any other projects were able to deploy anything because they
needed Teyla.
And that's what really sparked the movement.
So Subversion three, which is essentially this model without it, and I'll draw it out again.
But this is the big change in Helm too, versus Helm Ferry.
So now let's have a look at helm.
Very so said Helm three is the same as Helm wish to set up except Helm client.
Now, that really talks to the Cubans, this API and Cuba will keep track of any changes that did it
by default anyway, was also there to help the Helmholtz.
So now if we make a change to our deployment, Cubans will be aware of what's currently deployed and
the change we want to make and then we'll go ahead and make that change.
I'll also include a link, include some of the more subtle changes and held version free.
But this is the big one that Tela is no longer used.
And again, the big reason why it was such a problem is it would keep needing more resources because
it was keeping track of so much.
And if it went down battement, you can deploy anything.
So now we've been for what helmet's.
We now know how it works from an architectural point of view.
We're now ready to get started installing it and getting it on our machines.
I'll see in those lessons very shortly.