Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Helm
Helm

475
303
+ 1
5
KubeAdvisor
KubeAdvisor

0
1
+ 1
0
Add tool

Helm vs KubeAdvisor: What are the differences?

Developers describe Helm as "The Kubernetes Package Manager". Helm is the best way to find, share, and use software built for Kubernetes. On the other hand, KubeAdvisor is detailed as "It helps DevOps adopt best practices for Kubernetes". It helps teams adopt best practices to accelerate the adoption of Kubernetes, and optimize their existing stack, with machine learning. It scans K8s to make infrastructure and cloud-native applications reliable, resilient, and observable.

Helm and KubeAdvisor belong to "Container Tools" category of the tech stack.

Helm is an open source tool with 16.2K GitHub stars and 4.98K GitHub forks. Here's a link to Helm's open source repository on GitHub.

- No public GitHub repository available -

What is Helm?

Helm is the best way to find, share, and use software built for Kubernetes.

What is KubeAdvisor?

It helps teams adopt best practices to accelerate the adoption of Kubernetes, and optimize their existing stack, with machine learning. It scans K8s to make infrastructure and cloud-native applications reliable, resilient, and observable.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Helm?
Why do developers choose KubeAdvisor?
    Be the first to leave a pro
      Be the first to leave a con
        Be the first to leave a con
        What companies use Helm?
        What companies use KubeAdvisor?
          No companies found

          Sign up to get full access to all the companiesMake informed product decisions

          What tools integrate with Helm?
          What tools integrate with KubeAdvisor?

          Sign up to get full access to all the tool integrationsMake informed product decisions

          What are some alternatives to Helm and KubeAdvisor?
          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.
          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.
          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.
          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
          Decisions about Helm and KubeAdvisor
          Emanuel Evans
          Emanuel Evans
          Senior Architect at Rainforest QA · | 12 upvotes · 306.8K views
          atRainforest QARainforest QA
          Heroku
          Heroku
          Kubernetes
          Kubernetes
          Google Kubernetes Engine
          Google Kubernetes Engine
          Google Cloud SQL for PostgreSQL
          Google Cloud SQL for PostgreSQL
          PostgreSQL
          PostgreSQL
          Google Cloud Memorystore
          Google Cloud Memorystore
          Redis
          Redis
          CircleCI
          CircleCI
          Google Cloud Build
          Google Cloud Build
          Helm
          Helm
          Terraform
          Terraform

          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 · 172.3K views
          atDailyDaily
          Kubernetes
          Kubernetes
          GitHub
          GitHub
          CircleCI
          CircleCI
          Docker
          Docker
          Helm
          Helm

          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
          Russel Werner
          Russel Werner
          Lead Engineer at StackShare · | 0 upvotes · 12.3K views
          atStackShareStackShare
          Heroku
          Heroku
          Kubernetes
          Kubernetes
          Amazon EKS
          Amazon EKS
          Google Kubernetes Engine
          Google Kubernetes Engine
          Slack
          Slack
          Helm
          Helm
          CircleCI
          CircleCI
          Amazon EC2 Container Service
          Amazon EC2 Container Service

          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
          Robert Zuber
          Robert Zuber
          CTO at CircleCI · | 6 upvotes · 70.6K views
          atCircleCICircleCI
          Docker
          Docker
          Kubernetes
          Kubernetes
          Nomad
          Nomad
          Helm
          Helm

          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
          Interest over time
          Reviews of Helm and KubeAdvisor
          No reviews found
          How developers use Helm and KubeAdvisor
          No items found
          How much does Helm cost?
          How much does KubeAdvisor cost?
          Pricing unavailable
          News about Helm
          More news
          News about KubeAdvisor
          More news