1

00:00:00,640 --> 00:00:06,760

Now, you may already be thinking that deploying a stateful application in Carbonetti sounds complex,



2

00:00:07,000 --> 00:00:07,910

which it is.



3

00:00:08,230 --> 00:00:14,530

Plus, you also need some additional components like services and configuration to properly deploy that.



4

00:00:15,040 --> 00:00:18,090

That may require some application specific logic.



5

00:00:18,700 --> 00:00:26,800

So instead of each person in the world who needs to deploy ElasticSearch cluster in communities, creating



6

00:00:26,920 --> 00:00:35,290

their own set of configuration files for stateful said services, configuration and all sorts of things,



7

00:00:35,710 --> 00:00:43,030

a team of elastic put together this list of files and configured it correctly with all the needed configuration



8

00:00:43,180 --> 00:00:48,220

and put it into a distributable bundle for everyone else to use.



9

00:00:48,490 --> 00:00:55,150

And that bundle is a helme chart and the tool that is used to deploy that bundle is called help.



10

00:00:55,420 --> 00:01:02,440

So for most any stateful application, there is probably a health chart created and maintained by the



11

00:01:02,440 --> 00:01:08,630

experts on that application, which makes it easier for us all to deploy these applications in Bernardes.



12

00:01:08,860 --> 00:01:14,800

So how do we deploy them with a single comment, help install chart name?



13

00:01:14,980 --> 00:01:15,720

And that's it.



14

00:01:15,730 --> 00:01:21,250

You have the ElasticSearch application running in your cluster, replicated and configured.



15

00:01:21,520 --> 00:01:27,400

Each chart will also have a bunch of parameters so you can customize and adjust some attributes for



16

00:01:27,400 --> 00:01:28,020

deployment.



17

00:01:28,450 --> 00:01:35,260

For example, you can override the namespace name, you can change the replica count, storage, backend,



18

00:01:35,260 --> 00:01:38,200

etc., which will also do in the demo part.



19

00:01:38,890 --> 00:01:44,740

Once you deploy the application with Helme, you can also easily upgraded whenever a new version of



20

00:01:44,740 --> 00:01:51,760

the health chart comes out and also using simple Helmly lead command, you can clean up all the resources



21

00:01:51,760 --> 00:01:58,310

at once, doing the revert of Helme install instead of going and deleting each component one by one.



22

00:01:58,750 --> 00:02:05,380

Now, if you want to know more about stateful set and helme topics, I have much more detailed videos



23

00:02:05,380 --> 00:02:09,330

about them on my YouTube channel so you can check them out as well.