helm VS helmfile

Helm is an open-source platform that was created by DeisLabs. Helm is used as the package manager for Kubernetes. Many developers use Helm to install any Kubernetes application to the Kubernetes Cluster. Helm automates the process of deploying a Kubernetes application to the Kubernetes Cluster. Helms bundles a Kubernetes application into a single package known as a Helm chart. Developers will then take this Helm chart and install them on the Kubernetes Cluster. You can check this article on Sweet Code about deploying Helm Chart to Kubernetes.

There's no real reason, just manpower. At the end of the day, all these charts are based on a superset of functionality from Helm Charts. There are probably some variations in between the repos that would require some adjustment, so if anybody wants to help copy things over, as we say "Pull Requests Welcome" :)

Helm Chart is an open-source project owned by Kubernetes. It is Package Manager, Template Engine and Release engine for Kubernetes.

And I've found the issue https://github.com/helm/helm/issues/4256

If you want to compare Org with something on Github, a better comparison would be, say, helm - undoubtly popular package developed on Github. https://github.com/helm/helm/graphs/contributors Now, look at https://github.com/yantar92/org/graphs/contributors Again, I cannot help but notice that Org is more actively developed.

To take our journey one step further, we need the help of a very important tool in the K8s world: Helm. From their website: "Helm helps you manage Kubernetes applications — Helm Charts helps you define, install, and upgrade even the most complex Kubernetes application." Therefore, we need a "helm chart" to improve our deployment.

There are several ways how you can deploy a database in the cluster (you can also use a remote database hosted in the cloud, but we want to make this practice more challenging so we can touch more concepts regarding Kubernetes). You can manually write all the manifests (deployment, service, secrets, volumes, etc) or you can use **Helm **to deploy the database and many other services. I highly recommend using helm charts (verified ones) to deploy this kind of service instead of writing these by yourself.

Kubernetes and Helm for deployment

What do you mean by stored? The notebooks are deployed on kubernetes using Helm https://helm.sh (1 notebook = 1 Helm release), their configs are stored as Secrets on Kubernetes. If you mean data inside the notebook, one can enable persistence (mount a PersistenVolume into the notebook) (via the Helm values, see https://github.com/machine424/notebook-on-kube#create-connect-to-and-delete-a-notebook).

What we’re going to install into the newly created AKS cluster is located in the helm directory. The descriptive Helmfile approach enables us to define applications and their settings in the helmfile.yaml file.

Is there any alternative to https://github.com/roboll/helmfile you are currently using in your company.

Interesting, I have approached this problem using Helmfile (https://github.com/roboll/helmfile) to define a “platform release package.”

I agree; helm is too declarative.

Whenever I can, I use helmfile[0] for storing variables for helm since it does add a declarative layer on top of helm.

0 - https://github.com/roboll/helmfile

helmfile is something i’ve used in the past for this https://github.com/roboll/helmfile

I always felt like dependencies in helm are for very simple non-coupled packages. I many times use Helmfile (https://github.com/roboll/helmfile) to manage dependencies instead of banging my head with vanilla Helm.

Once you do that, learn to create dynamic helm charts that use go templating and conditionals: https://github.com/roboll/helmfile

helmfile is not widely known but awesomeme

Not exactly an answer to your question, but we have created a separate project called "cluster" where we define all cluster dependencies via https://github.com/roboll/helmfile, meaning that you always know what (+versions) you have in the cluster and can easily reproduce it. It does not solve an issue with knowing what project has a new version now but at least you can be sure what version is in your cluster

Dont.Use.Umbrella.Charts. If you need to deploy multiple things at once, but you dont wanna deal with relative complexity of Flux or ArgoCD - use helmfile. https://github.com/roboll/helmfile