278
135
+ 1
4

What is Helm?

Helm is the best way to find, share, and use software built for Kubernetes.
Helm is a tool in the Container Tools category of a tech stack.
Helm is an open source tool with 13.9K GitHub stars and 4.5K GitHub forks. Here’s a link to Helm's open source repository on GitHub

Who uses Helm?

Companies
131 companies reportedly use Helm in their tech stacks, including CircleCI, Docplanner, and www.autotrader.co.uk.

Developers
135 developers on StackShare have stated that they use Helm.

Helm Integrations

Docker, Polyaxon, Continuous Delivery Service, Konstellate, and Loki are some of the popular tools that integrate with Helm. Here's a list of all 7 tools that integrate with Helm.

Why developers like Helm?

Here’s a list of reasons why companies and developers use Helm
Helm Reviews

Here are some stack decisions, common use cases and reviews by companies and developers who chose Helm in their tech stack.

Emanuel Evans
Emanuel Evans
Senior Architect at Rainforest QA · | 12 upvotes · 80.8K views
atRainforest QARainforest QA
Terraform
Terraform
Helm
Helm
Google Cloud Build
Google Cloud Build
CircleCI
CircleCI
Redis
Redis
Google Cloud Memorystore
Google Cloud Memorystore
PostgreSQL
PostgreSQL
Google Cloud SQL for PostgreSQL
Google Cloud SQL for PostgreSQL
Google Kubernetes Engine
Google Kubernetes Engine
Kubernetes
Kubernetes
Heroku
Heroku

We recently moved our main applications from Heroku to Kubernetes . The 3 main driving factors behind the switch were scalability (database size limits), security (the inability to set up PostgreSQL instances in private networks), and costs (GCP is cheaper for raw computing resources).

We prefer using managed services, so we are using Google Kubernetes Engine with Google Cloud SQL for PostgreSQL for our PostgreSQL databases and Google Cloud Memorystore for Redis . For our CI/CD pipeline, we are using CircleCI and Google Cloud Build to deploy applications managed with Helm . The new infrastructure is managed with Terraform .

Read the blog post to go more in depth.

See more
Ido Shamun
Ido Shamun
at The Elegant Monkeys · | 6 upvotes · 21K views
atDailyDaily
Helm
Helm
Docker
Docker
CircleCI
CircleCI
GitHub
GitHub
Kubernetes
Kubernetes

Kubernetes powers our #backend services as it is very easy in terms of #devops (the managed version). We deploy everything using @helm charts as it provides us to manage deployments the same way we manage our code on GitHub . On every commit a CircleCI job is triggered to run the tests, build Docker images and deploy them to the registry. Finally on every master commit CircleCI also deploys the relevant service using Helm chart to our Kubernetes cluster

See more
Robert Zuber
Robert Zuber
CTO at CircleCI · | 6 upvotes · 7.4K views
atCircleCICircleCI
Helm
Helm
Nomad
Nomad
Kubernetes
Kubernetes
Docker
Docker

Our backend consists of two major pools of machines. One pool hosts the systems that run our site, manage jobs, and send notifications. These services are deployed within Docker containers orchestrated in Kubernetes. Due to Kubernetes’ ecosystem and toolchain, it was an obvious choice for our fairly statically-defined processes: the rate of change of job types or how many we may need in our internal stack is relatively low.

The other pool of machines is for running our users’ jobs. Because we cannot dynamically predict demand, what types of jobs our users need to have run, nor the resources required for each of those jobs, we found that Nomad excelled over Kubernetes in this area.

We’re also using Helm to make it easier to deploy new services into Kubernetes. We create a chart (i.e. package) for each service. This lets us easily roll back new software and gives us an audit trail of what was installed or upgraded.

See more
Richard Whitehead
Richard Whitehead
CTO, Evangelist in Chief at Moogsoft Inc. · | 1 upvotes · 2.8K views
atMoogsoftMoogsoft
Helm
Helm
Kubernetes
Kubernetes

For container management, we selected Kubernetes, for it's maturity, and ecosystem (Helm etc.)

See more
Russel Werner
Russel Werner
Lead Engineer at StackShare · | 0 upvotes · 2.6K views
atStackShareStackShare
Amazon EC2 Container Service
Amazon EC2 Container Service
CircleCI
CircleCI
Helm
Helm
Slack
Slack
Google Kubernetes Engine
Google Kubernetes Engine
Amazon EKS
Amazon EKS
Kubernetes
Kubernetes
Heroku
Heroku

We began our hosting journey, as many do, on Heroku because they make it easy to deploy your application and automate some of the routine tasks associated with deployments, etc. However, as our team grew and our product matured, our needs have outgrown Heroku. I will dive into the history and reasons for this in a future blog post.

We decided to migrate our infrastructure to Kubernetes running on Amazon EKS. Although Google Kubernetes Engine has a slightly more mature Kubernetes offering and is more user-friendly; we decided to go with EKS because we already using other AWS services (including a previous migration from Heroku Postgres to AWS RDS). We are still in the process of moving our main website workloads to EKS, however we have successfully migrate all our staging and testing PR apps to run in a staging cluster. We developed a Slack chatops application (also running in the cluster) which automates all the common tasks of spinning up and managing a production-like cluster for a pull request. This allows our engineering team to iterate quickly and safely test code in a full production environment. Helm plays a central role when deploying our staging apps into the cluster. We use CircleCI to build docker containers for each PR push, which are then published to Amazon EC2 Container Service (ECR). An upgrade-operator process watches the ECR repository for new containers and then uses Helm to rollout updates to the staging environments. All this happens automatically and makes it really easy for developers to get code onto servers quickly. The immutable and isolated nature of our staging environments means that we can do anything we want in that environment and quickly re-create or restore the environment to start over.

The next step in our journey is to migrate our production workloads to an EKS cluster and build out the CD workflows to get our containers promoted to that cluster after our QA testing is complete in our staging environments.

See more

Helm Alternatives & Comparisons

What are some alternatives to Helm?
Terraform
With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.
Kubernetes
Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
Docker Compose
With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.
Rancher
Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.
Docker Swarm
Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.
See all alternatives

Helm's Followers
135 developers follow Helm to keep up with related blogs and decisions.
Palmtree  labs
Jeff Cunningham
Andy Hall
Krishnan Subramanian
Dave Mackey
vikrant singh
vadimiljin
Urbano Gutierrez
yungnelly
john marbach