Now, you may already be thinking that deploying a stateful application in Carbonetti sounds complex,
which it is.
Plus, you also need some additional components like services and configuration to properly deploy that.
That may require some application specific logic.
So instead of each person in the world who needs to deploy ElasticSearch cluster in communities, creating
their own set of configuration files for stateful said services, configuration and all sorts of things,
a team of elastic put together this list of files and configured it correctly with all the needed configuration
and put it into a distributable bundle for everyone else to use.
And that bundle is a helme chart and the tool that is used to deploy that bundle is called help.
So for most any stateful application, there is probably a health chart created and maintained by the
experts on that application, which makes it easier for us all to deploy these applications in Bernardes.
So how do we deploy them with a single comment, help install chart name?
And that's it.
You have the ElasticSearch application running in your cluster, replicated and configured.
Each chart will also have a bunch of parameters so you can customize and adjust some attributes for
deployment.
For example, you can override the namespace name, you can change the replica count, storage, backend,
etc., which will also do in the demo part.
Once you deploy the application with Helme, you can also easily upgraded whenever a new version of
the health chart comes out and also using simple Helmly lead command, you can clean up all the resources
at once, doing the revert of Helme install instead of going and deleting each component one by one.
Now, if you want to know more about stateful set and helme topics, I have much more detailed videos
about them on my YouTube channel so you can check them out as well.