Overall Satisfaction with Helm
We are also using Terraform for deployment, but it's more suited for new deployments and specific use cases. Helm takes the lead in terms of containers software package management, and it addresses our use case of ensuring all software packages deployment are uniform, secure - from a trusted repository, rapid deployment and rollbacks.
- Templates - The ability to create templates is really helpful and help creates a baseline for package management.
- Rollbacks - it is godsend. Period.
- Dry-run - This really is helpful when troubleshooting deployments and is great for testing out new charts as well.
- It would be great if there is verbose mode in Helm errors. Not sure if it's a thing. But more detail in the errors do helps, at times.
- Reuse. Reuse. Reuse.
- Reduction in human effort.
- Streamline software versions and upgrades.
- Terraform and by HashiCorp
We use Terraform as well. But Terraform is more suited for new deployments and specific use cases. For Helm, it is especially well suited for large scale cloud instances software deployment, by helping us to keep track of software components and versions centrally, and automated deployments is a huge plus.
Do you think Helm delivers good value for the price?
Are you happy with Helm's feature set?
Did Helm live up to sales and marketing promises?
Did implementation of Helm go as expected?
Would you buy Helm again?
Deployment of helm charts is really fundamental to any software packages to our Kubernetes/docker containers, and without Helm, I cannot imagine how else to manage software components upgrades. When it works, it works great, when it doesn't - the world has not come to an end, there is rollback, and it's great, but troubleshooting does take time. And there is a learning curve. But it be worth it.